Template development based on reported aspects of a plurality of source users

ABSTRACT

A computationally implemented method includes, but is not limited to: providing a plurality of relevant reported aspects associated with a plurality of source users that are relevant to achieving one or more target outcomes, the providing of the plurality of relevant reported aspects being based, at least in part, on relevancy of the plurality of relevant reported aspects with respect to the one or more target outcomes; and developing a template designed to facilitate one or more end users to achieve the one or more target outcomes when one or more emulatable aspects included in the template are emulated, the development of the template being based, at least in part, on the providing of the plurality of relevant reported aspects associated with the plurality of source users In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to and claims the benefit of theearliest available effective filing date(s) from the following listedapplication(s) (the “Related Applications”) (e.g., claims earliestavailable priority dates for other than provisional patent applicationsor claims benefits under 35 USC §119(e) for provisional patentapplications, for any and all parent, grandparent, great-grandparent,etc. applications of the Related Application(s)). All subject matter ofthe Related Applications and of any and all parent, grandparent,great-grandparent, etc. applications of the Related Applications isincorporated herein by reference to the extent such subject matter isnot inconsistent herewith.

RELATED APPLICATIONS

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/584,489, entitled PERSONALIZED PLAN DEVELOPMENT,naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y.Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T.Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T.Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 3Sep. 2009, which is currently co-pending, or is an application of whicha currently co-pending application is entitled to the benefit of thefiling date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/584,653, entitled PERSONALIZED PLAN DEVELOPMENT,naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y.Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T.Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T.Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 8Sep. 2009, which is currently co-pending, or is an application of whicha currently co-pending application is entitled to the benefit of thefiling date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/587,018, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON OUTCOME IDENTIFICATION, naming Shawn P. Firminger; Jason Garms;Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 29 Sep. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/587,127, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON OUTCOME IDENTIFICATION, naming Shawn P. Firminger; Jason Garms;Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 30 Sep. 2009, now U.S. Pat. No.8,229,756 which is currently co-pending, or is an application of which acurrently co-pending application is entitled to the benefit of thefiling date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/590,027, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON ONE OR MORE REPORTED ASPECTS' ASSOCIATION WITH ONE OR MORESOURCE USERS, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde;Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A.Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D.Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood,Jr. as inventors, filed 29 Oct. 2009, which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/590,039, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON ONE OR MORE REPORTED ASPECTS' ASSOCIATION WITH ONE OR MORESOURCE USERS, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde;Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A.Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D.Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood,Jr. as inventors, filed 30 Oct. 2009, which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/590,600, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON IDENTIFICATION OF ONE OR MORE RELEVANT REPORTED ASPECTS, namingShawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung;Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord;Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T.Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 10Nov. 2009, now U.S. Pat. No. 8,234,123 which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/590,841, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON IDENTIFICATION OF ONE OR MORE RELEVANT REPORTED ASPECTS, namingShawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung;Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord;Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T.Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 12Nov. 2009, which is currently co-pending, or is an application of whicha currently co-pending application is entitled to the benefit of thefiling date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/592,075, entitled DEVELOPMENT OF PERSONALIZEDPLANS BASED ON ACQUISITION OF RELEVANT REPORTED ASPECTS, naming Shawn P.Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D.Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; RobertW. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene;Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 17 Nov. 2009,which is currently co-pending, or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/592,161, entitled DEVELOPMENT OF PERSONALIZEDPLANS BASED ON ACQUISITION OF RELEVANT REPORTED ASPECTS, naming Shawn P.Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D.Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; RobertW. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene;Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 18 Nov. 2009,which is currently co-pending, or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/592,544, entitled IDENTIFICATION AND PROVISIONOF REPORTED ASPECTS THAT ARE RELEVANT WITH RESPECT TO ACHIEVEMENT OFTARGET OUTCOMES, naming Shawn P. Firminger; Jason Garms; Roderick A.Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A.Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D.Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood,Jr. as inventors, filed 24 Nov. 2009, which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/592,548, entitled IDENTIFICATION AND PROVISIONOF REPORTED ASPECTS THAT ARE RELEVANT WITH RESPECT TO ACHIEVEMENT OFTARGET OUTCOMES, naming Shawn P. Firminger; Jason Garms; Roderick A.Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A.Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D.Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood,Jr. as inventors, filed 25 Nov. 2009, which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/592,944, entitled TEMPLATE DEVELOPMENT BASED ONSENSOR ORIGINATED REPORTED ASPECTS, naming Shawn P. Firminger; JasonGarms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 3 Dec. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/592,946, entitled TEMPLATE DEVELOPMENT BASED ONSENSOR ORIGINATED REPORTED ASPECTS, naming Shawn P. Firminger; JasonGarms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 4 Dec. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/653,117, entitled SOURCE USER BASED PROVISION OFONE OR MORE TEMPLATES, naming Shawn P. Firminger; Jason Garms; RoderickA. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; RoyceA. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D.Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood,Jr. as inventors, filed 7 Dec. 2009, which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/653,180, entitled SOURCE USER BASED PROVISION OFONE OR MORE TEMPLATES, naming Shawn P. Firminger; Jason Garms; RoderickA. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; RoyceA. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D.Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood,Jr. as inventors, filed 8 Dec. 2009, which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/653,387, entitled TARGET OUTCOME BASED PROVISIONOF ONE OR MORE TEMPLATES, naming Shawn P. Firminger; Jason Garms;Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 10 Dec. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/653,386, entitled TARGET OUTCOME BASED PROVISIONOF ONE OR MORE TEMPLATES, naming Shawn P. Firminger; Jason Garms;Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 11 Dec. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/653,972, entitled DETECTING DEVIATION FROMCOMPLIANT EXECUTION OF A TEMPLATE, naming Shawn P. Firminger; JasonGarms; Roderick A. Hyde; Edward K.Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 17 Dec. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/655,075, entitled DETECTING DEVIATION FROMCOMPLIANT EXECUTION OF A TEMPLATE, naming Shawn P. Firminger; JasonGarms; Roderick A. Hyde; Edward K.Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 21 Dec. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/655,250, entitled TEMPLATE MODIFICATION BASED ONDEVIATION FROM COMPLIANT EXECUTION OF THE TEMPLATE, naming Shawn P.Firminger; Jason Garms; Roderick A. Hyde; Edward K.Y. Jung; Chris D.Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; RobertW. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene;Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 23 Dec. 2009,which is currently co-pending, or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/655,365, entitled TEMPLATE MODIFICATION BASED ONDEVIATION FROM COMPLIANT EXECUTION OF THE TEMPLATE, naming Shawn P.Firminger; Jason Garms; Roderick A. Hyde; Edward K.Y. Jung; Chris D.Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; RobertW. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene;Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 28 Dec. 2009,which is currently co-pending, or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

The United States Patent Office (USPTO) has published a notice to theeffect that the USPTO's computer programs require that patent applicantsreference both a serial number and indicate whether an application is acontinuation or continuation-in-part. Stephen G. Kunin, Benefit ofPrior-Filed Application, USPTO Official Gazette Mar. 18, 2003, availableat http://www.uspto.gov/web/offices/com/sol/og/2003/week11/patbene.htm.The present Applicant Entity (hereinafter “Applicant”) has providedabove a specific reference to the application(s) from which priority isbeing claimed as recited by statute. Applicant understands that thestatute is unambiguous in its specific reference language and does notrequire either a serial number or any characterization, such as“continuation” or “continuation-in-part,” for claiming priority to U.S.patent applications. Notwithstanding the foregoing, Applicantunderstands that the USPTO's computer programs have certain data entryrequirements, and hence Applicant is designating the present applicationas a continuation-in-part of its parent applications as set forth above,but expressly points out that such designations are not to be construedin any way as any type of commentary and/or admission as to whether ornot the present application contains any new matter in addition to thematter of its parent application(s).

SUMMARY

A computationally implemented method includes, but is not limited toproviding a plurality of relevant reported aspects associated with aplurality of source users that are relevant to achieving one or moretarget outcomes, the providing of the plurality of relevant reportedaspects being based, at least in part, on relevancy of the plurality ofrelevant reported aspects with respect to the one or more targetoutcomes; and developing a template designed to facilitate one or moreend users to achieve the one or more target outcomes when one or moreemulatable aspects included in the template are emulated, thedevelopment of the template being based, at least in part, on theproviding of the plurality of relevant reported aspects associated withthe plurality of source users. In addition to the foregoing, othermethod aspects are described in the claims, drawings, and text forming apart of the present disclosure.

In one or more various aspects, related systems include but are notlimited to circuitry and/or programming for effecting theherein-referenced method aspects; the circuitry and/or programming canbe virtually any combination of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

A computationally implemented system includes, but is not limited to:means for providing a plurality of relevant reported aspects associatedwith a plurality of source users that are relevant to achieving one ormore target outcomes, the providing of the plurality of relevantreported aspects being based, at least in part, on relevancy of theplurality of relevant reported aspects with respect to the one or moretarget outcomes; and means for developing a template designed tofacilitate one or more end users to achieve the one or more targetoutcomes when one or more emulatable aspects included in the templateare emulated, the development of the template being based, at least inpart, on the providing of the plurality of relevant reported aspectsassociated with the plurality of source users. In addition to theforegoing, other system aspects are described in the claims, drawings,and text forming a part of the present disclosure.

A computationally implemented system includes, but is not limited to:circuitry for providing a plurality of relevant reported aspectsassociated with a plurality of source users that are relevant toachieving one or more target outcomes, the providing of the plurality ofrelevant reported aspects being based, at least in part, on relevancy ofthe plurality of relevant reported aspects with respect to the one ormore target outcomes; and circuitry for developing a template designedto facilitate one or more end users to achieve the one or more targetoutcomes when one or more emulatable aspects included in the templateare emulated, the development of the template being based, at least inpart, on the providing of the plurality of relevant reported aspectsassociated with the plurality of source users. In addition to theforegoing, other system aspects are described in the claims, drawings,and text forming a part of the present disclosure.

A computer program product including a signal-bearing medium bearing oneor more instructions for providing a plurality of relevant reportedaspects associated with a plurality of source users that are relevant toachieving one or more target outcomes, the providing of the plurality ofrelevant reported aspects being based, at least in part, on relevancy ofthe plurality of relevant reported aspects with respect to the one ormore target outcomes; and one or more instructions for developing atemplate designed to facilitate one or more end users to achieve the oneor more target outcomes when one or more emulatable aspects included inthe template are emulated, the development of the template being based,at least in part, on the providing of the plurality of relevant reportedaspects associated with the plurality of source users. In addition tothe foregoing, other computer program product aspects are described inthe claims, drawings, and text forming a part of the present disclosure.

A method for developing a template based, at least in part, on aplurality of relevant reported aspects associated with a plurality ofsource users, the method includes providing a plurality of relevantreported aspects associated with a plurality of source users that arerelevant to achieving one or more target outcomes, the providing of theplurality of relevant reported aspects being based, at least in part, onrelevancy of the plurality of relevant reported aspects with respect tothe one or more target outcomes; and developing, using a processor, atemplate designed to facilitate one or more end users to achieve the oneor more target outcomes when one or more emulatable aspects included inthe template are emulated, the development of the template being based,at least in part, on the providing of the plurality of relevant reportedaspects associated with the plurality of source users.

The foregoing summary is illustrative only and is not intended to be inany way limiting. In addition to the illustrative aspects, embodiments,and features described above, further aspects, embodiments, and featureswill become apparent by reference to the drawings and the followingdetailed description.

BRIEF DESCRIPTION OF THE FIGURES

FIGS. 1 a and 1 b show a high-level block diagram of a Computing Device10 operating in a network environment.

FIG. 2 a shows another perspective of the Relevant Reported AspectProviding module 102 of the Computing Device 10 of FIG. 1 b.

FIG. 2 b shows another perspective of the Template Developing Module 104of the Computing Device 10 of FIG. 1 b.

FIG. 3 is a high-level logic flowchart of a process.

FIG. 4 a is a high-level logic flowchart of a process depictingalternate implementations of the relevant reported aspect providingoperation 302 of FIG. 3.

FIG. 4 b is a high-level logic flowchart of a process depictingalternate implementations of the relevant reported aspect providingoperation 302 of FIG. 3.

FIG. 4 c is a high-level logic flowchart of a process depictingalternate implementations of the relevant reported aspect providingoperation 302 of FIG. 3.

FIG. 4 d is a high-level logic flowchart of a process depictingalternate implementations of the relevant reported aspect providingoperation 302 of FIG. 3.

FIG. 4 e is a high-level logic flowchart of a process depictingalternate implementations of the relevant reported aspect providingoperation 302 of FIG. 3.

FIG. 5 a is a high-level logic flowchart of a process depictingalternate implementations of the template developing operation 304 ofFIG. 3.

FIG. 5 b is a high-level logic flowchart of a process depictingalternate implementations of the template developing operation 304 ofFIG. 3.

FIG. 5 c is a high-level logic flowchart of a process depictingalternate implementations of the template developing operation 304 ofFIG. 3.

FIG. 5 d is a high-level logic flowchart of a process depictingalternate implementations of the template developing operation 304 ofFIG. 3.

FIG. 5 e is a high-level logic flowchart of a process depictingalternate implementations of the template developing operation 304 ofFIG. 3.

FIG. 6 is a high-level logic flowchart of another process.

FIG. 7 is a high-level logic flowchart of a process depicting alternateimplementations of the template presenting operation 606 of FIG. 6.

FIG. 8 is another high-level block diagram showing one implementation ofthe computing device 10 of FIG. 1 b.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented here.

A recent trend that has enjoyed explosive popularity in thecomputing/communication field is to electronically record one's dailyactivities, behaviors, thoughts, beliefs, traits, physical or mentalstates, physical characteristics, and other aspects of the person'severyday life onto an open diary. One place where such open diaries aremaintained is at social networking sites commonly known as “blogs” whereone or more users may report or post every aspect of their daily lives.In brief, an “aspect,” as will be referred to herein, may be inreference to any act, behavior, characteristic, user state or status,belief, external events, and so forth, that may be associated with auser (e.g., a person including, for example, a network user such as ablogger or a social networking user). The process of reporting orposting blog entries is commonly referred to as “blogging.” A newer typeof blogging that has quickly become ubiquitous in the social networkingfabric is “microblogging,” colloquially referred to as “twittering” or“tweeting.” In microblogging, each of the microblogs that are posted aretypically relatively short posts or entries, usually not more than 140characters long.

Other types of social networking sites may also allow users to maintainopen diaries and to allow users to easily update their personalinformation in real time. Such updates are typically made via, forexample, social networking status reports otherwise known simply as“status reports.” These social networking sites allow a user to reportor post for others to view the latest status or other aspects related tothe user.

Another recent tread in social networking is to employ one or moresensors to detect and report on a wide variety of user aspects (i.e.,aspects of a user). Examples of sensors that may be used for suchpurposes vary widely, ranging from well-known devices that can detectand report on various physiological parameters such as heart rate orblood pressure, to sensors that can detect certain user behaviors oractivities such as toilet usage. Examples of sensors that may beemployed in order to monitor or detect user activities include, forexample, accelerometers, pedometers, global positioning systems or GPSs,and so forth. Such devices are already, in fact, being integrated intomobile computing/communication devices such as cellular telephones andsmart phones, and even into functional devices such as automobiles,exercise machines, household appliances, and so forth.

Other types of sensors are also being integrated into mobilecomputing/communication devices such as those that monitor environmentalconditions. Examples of such sensors include, for example, those thatcan measure atmospheric conditions such as air quality levels. In somecases, sensors may be integrated into functional devices such asautomobiles, exercise machines, household appliances, and so forth inorder to detect and monitor, for example, their usage as well as, insome cases certain physical or physiological characteristics of thedevice operators. There are also sensors that are currently availablethat can even monitor bathroom or toilet usage. All the above describedsensors may be configured to provide their collected data through logentries such as entries made through social networking channels (e.g.,microblogs, blogs, social networking internet sites, and so forth).

Although a wealth of personal information provided through log entries(e.g., microblogs, status reports, and so forth) are now availablethrough such social networking internet sites (or simply “socialnetworking sites”), it is only recently has there been any effort toexploit such potentially useful data. As blogs, microblogs, and varioussocial networking sites become increasingly popular, personal datacollected through such means may be spread across multiple networklocations.

One possible way to exploit such personal data is to use such data todevelop templates for achieving a variety of target outcomes (e.g.,goals) based on the personal data. In brief, a template may be a plan, aprogram, or a schedule that is designed to facilitate one or more endusers to achieve one or more target outcomes when one or more events(i.e., in the following descriptions, these events will be referred toas “emulatable aspects”) that may be included with the template areemulated. In other words, to use personal data of those (e.g., sourceusers) who have already achieved desirable goals (e.g., target outcomes)to develop templates for others (e.g., end users) to emulate in order tofacilitate them in achieving those goals.

Each of the one or more emulatable aspects that may be included in atemplate may be based on and correspond to one or more reported aspectsof one or more source users that may have been reported through, forexample, social networking channels (e.g., microblogs, social networkingsites, and so forth). An “aspect,” in brief may be any behavior, act,mental state, physical state, and so forth that may be associated with asource user. A “reported aspect” is any aspect associated with a sourceuser that may have been reported via, for example, one or more socialnetworking channels or by other means.

There are at least two types of templates that could be developed frompersonal data obtained through, for example, social networking channels.One type of templates that can be developed is generic templates thatmay be designed to be used generically by any random user in order toachieve one or more target outcomes. The second type of templates, whichmay be referred to as personalized templates or personalized plans,include those templates that have been personalized for use by aparticular end user or users (e.g., a modified version of a generictemplate that has been modified in order to accommodate the end user'slimitations and/or preferences). For purposes of this description,references to a “template” in the following will be in reference toeither the first or the second type of templates.

In various embodiments, methods, systems, circuitry, and computerprogram products are provided that are designed to develop a templatethat is designed to facilitate one or more end users to achieve one ormore target outcomes when one or more emulatable aspects included in thetemplate are emulated, the development of the template being based, atleast in part, on relevant reported aspects of a plurality of sourceusers, the relevant reported aspects being relevant to achieving the oneor more target outcomes. In some embodiments, the relevant reportedaspects of the plurality of source users may have been originallyreported via log entries such as microblog entries and status reports.More generally, the methods, systems, circuitry, and computer programproducts to be provided are designed to facilitate the development of atemplate based on reported aspects of multiple source users. Thesemethods, systems, circuitry, and computer program products being verydynamic and are able to facilitate in the development of almost any typeof template to achieve almost any type of target outcomes.

As previously described a “template” may be any type of plan, program,or schedule that is designed to facilitate achievement of one or moretarget outcomes when one or more emulatable aspects included in thetemplate are emulated. Each of the one or more emulatable aspects thatmay be included in the template may have been developed based on aplurality of relevant reported aspects that are each associated with adifferent source user. In various embodiments, each of the associatedsource users may or may not have originally reported the associatedrelevant reported aspect. That is, a reported aspect (e.g., a relevantor non-relevant reported aspect) of a source user may be reported by anyone of a number of different sources including, for example, by thesource user (e.g., a microblogger or a social networking user) who isthe basis for the reported aspect, by a sensor, or by a third party(e.g., such as another source user).

As briefly described earlier, a template may comprise of one or moreemulatable aspects that may be based on reported aspects of, forexample, one or more source users. Note that the word “emulatable” aswill be repeatedly used herein has no significant meaning other than tobe used in the following description to merely distinguish those aspects(emulatable aspects) that are indicated in a template from other typesof aspects (e.g., reported aspects of source users). In accordance withvarious embodiments, a template may be developed for achieving almostany type of desired outcome (e.g., target outcome) so long as theappropriate data, such as log entry data of source users who haveachieved the desired outcome, are available. Examples of the types oftemplates that could be developed based on log entry data include, forexample, those that are designed to facilitate achievement of medical orhealth related outcomes, those that are designed to facilitateachievement of athletic or gaming outcomes, those that are designed tofacilitate achievement of particular user states such as mental orsocial states, those that are designed to facilitate achievement ofintellectual or academic outcomes, and so forth.

In some cases, a template may merely indicate or be a collection of oneor more emulatable aspects that end users may emulate in order toachieve one or more target outcomes. In other instances, however, atemplate may indicate a plurality of emulatable aspects and may definetheir relationships (e.g., temporal or specific time relationship) withrespect to each other. Such a template will be very similar to aschedule or program that indicates when each of the emulatable aspectsincluded in the template should be emulated by end users with respect tothe other emulatable aspects included in the template. For example, if atemplate is designed to facilitate end users to shed a certain amount ofbody weight, it may include a schedule of when and what activities(e.g., go jogging for 30 minutes on day 1, go swimming for 40 minutes onday 2, and so forth) end users may need to execute in order to achievethe weight loss. Similarly, if the template is designed to, for example,facilitate end users to achieve a high score for the scholastic aptitudetest (SAT), the template may be a schedule of when and what activities(e.g., read a particular book on day 1, work on math problems from aparticular math book on day 2, and so forth) end users may need toexecute in order to achieve the high test score for the SAT.

In some instances a template may include one or more emulatableintermediate outcomes that are related to the one or more targetoutcomes associated with the template. For example, in the above weightloss example, the template may indicate the amount of weight loss endusers should have achieved (e.g., in order to achieve the targetoutcome) after emulating, for example, one week, two weeks, or a monthof emulatable aspects indicated by the template.

In still other cases, a template may merely be a collection ofemulatable aspects that does not define the relationships between theemulatable aspects. For example, a template designed to facilitate anend user to achieve relaxed state of mind may indicate two unlinkedemulatable aspects, “get 8 hours of sleep each night,” and “avoidcaffeine beverages.” Such a template would not necessarily have anyindication of relationship between the two emulatable aspects indicatedby the template. It should be noted here that an emulatable aspect thatmay be included into a template may not only be an act or a behavior,but may be a physiological characteristic, a mental state, or any otheraspect that may be emulated. For example, a template that is designed tofacilitate reducing backaches may include as one of its aspects, arequirement to keep blood pressure below a certain level, which is aphysiological state. An emulatable aspect may even be an external event,such as environmental conditions, that an end user may have some controlover.

In some embodiments, a template may include or be linked to otherinformation other than emulatable aspects. For example, in someinstances, a template may include or be associated with a particularsource user and/or with a particular target outcome. Other informationmay also be included with or be associated with a template as will befurther described herein.

In order to facilitate understanding of the various concepts to bedescribed herein, an introduction to the meaning of certain words andphrases to be used in the following discussion will now be provided. Asdescribed earlier, an “aspect” may be any occurrence of any behavior,act, belief, characteristic, user state or status, external event, orany other facet associated with a source user or a group of sourceusers. A “source user” may be any person, such as a microblogger or asocial networking user, who may be the basis for one or more reportedaspects. Note that a source user may not necessarily have to be thesource for the one or more reported aspects that are related to thesource user since reported aspects that are associated with a particularsource user may be provided by other source users or by sensors.

A “reported aspect” may be any aspect associated with or related to asource user or an end user that has been reported by, for example, thesource user, the end user, one or more sensors, or one or more thirdparties (e.g., other source users or end users). In some instances, sucha reported aspect may be reported in the form of a log entry such as amicroblog entry, a status report, or a journal entry.

A “target outcome” may be any type of desirable goal or result that maybe sought by, for example, end users. Examples of target outcomesinclude, for example, health-related outcomes such as weight loss orimproved cardiovascular conditioning, athletic outcomes such asdeveloping a particular athletic skill including being able to pitch acurve ball or achieving a particular golf handicap, physiologicaloutcomes such as reduced blood pressure or blood glucose levels, socialoutcomes such as obtaining membership into an elite social club orattaining a particular social status, mental state outcomes such asachieving certain level of calmness or happiness, interpersonal orrelational outcomes such as having lots of friends or developing skillto make friends, employment outcomes such as being promoted ordeveloping certain work skills, academic or intellectual outcomes, andso forth.

An “end user” may be any person, for example, who executes a template inorder to achieve one or more target outcomes. As briefly describedabove, a “source user” may be any person who may be the basis for one ormore reported aspects. Note that although in most cases, a source userwill be an actual (real) person who may be the basis for one or morereported aspects, in other cases, however, a source user may be afictional person such as a composite of multiple “actual” source users.For example, reported aspects indicating actual aspects of a pluralityof actual source users may be compiled and processed (e.g., normalizedor averaged out) in order to create a fictional source user.

Turning now to FIGS. 1 a, and 1 b illustrating an example environment inwhich the methods, systems, circuitry, and computer program products inaccordance with various embodiments may be implemented by a computingdevice 10. In particular, the methods, systems, circuitry, and computerprogram products may be implemented at any network device including at apeer-to-peer network component device. In some embodiments, thecomputing device 10 may be a server such as one of the one or morenetwork servers 60 illustrated in FIG. 1 a. Alternatively, the computingdevice 10 may be a source user device such as one of the local sourceuser devices 20* illustrated in FIG. 1 a. In still other embodiments,the computing device 10 may be an end user device such as one of thelocal end user devices 30* illustrated in FIG. 1 a. Note that in thefollowing, “*” represents a wildcard. Thus, references in the followingdescription to, for example, “a source user 2*” may be in reference to asource user 2 a, a source user 2 b, a source user 2 c, and so forth, ora combination thereof.

Note further that for ease of understanding and explanation, thecomputing device 10 of the exemplary environment 100 of FIGS. 1 a and 1b in the following discussion will be generally described operating as aserver (e.g., server embodiment) rather than as an end user device or asa source user device. Further, although the following discussion relatedto the exemplary environment 100 of FIGS. 1 a and 1 b assumes that thecomputing device 10 is a server, the following discussion will, for themost part, be applicable even if the computing device 10 were operatingas an end user device (e.g., local end user device 30*) or as a sourceuser device (e.g., local source user device 20*) with certain obviousexceptions (e.g., if the computing device 10 is an end user device or asource user device rather than a server, the computing device 10 maycommunicate with an end user 4* or a source user 2* directly through auser interface 120 rather than indirectly through one or morecommunication networks 50 as may be the case when the computing device10 is a server). In some embodiments, the computing device 10 mayoperate via a web 1.0 or web 2.0 construct.

Referring back to FIGS. 1 a and 1 b, and as previously indicated, thecomputing device 10 may be a network device such as a server (e.g., anetwork server 60) that is designed to communicate with other networkdevices. For example, the computing device 10 may communicate with oneor more source users 2* (e.g., source user 2 a, source user 2 b, sourceuser 2 c, source user 2 d, and so forth) through one or more localsource user devices 20* (e.g., local source user device 20 a, localsource user device 20 b, and so forth), with a plurality of end users 4*(e.g., end user 4 a, end user 4 b, and so forth) through a plurality oflocal end user devices 30* (e.g., local end user device 30 a, local enduser device 30 b, and so forth), with one or more sensor integrateddevices 40 (e.g., a transportation vehicle such as a car, an exercisemachine, or any other type of functional device that may have anintegrated sensor designed to sense, for example, their usage or someaspect of the device operator), with one or more network servers 60,and/or with one or more third parties 6 (e.g., one or more contentproviders, one or more network service providers, and/or one or morepotential future end users 4*) via one or more communication networks50. In some implementations, the one or more communication networks 50may include one or more wireless networks and/or one or more wirednetworks including, for example, at least one of a local area network(LAN), a wireless local area network (WLAN), personal area network(PAN), Worldwide Interoperability for Microwave Access (WiMAX), publicswitched telephone network (PTSN), general packet radio service (GPRS),cellular networks, and/or other types of wireless and/or wired networks.

In some implementations, the computing device 10 may be designed todevelop at least one template 16 that is designed to facilitate one ormore end users 4* to achieve one or more target outcomes when one ormore emulatable aspects included in the template 16 are emulated. Thedevelopment of the template 16 may be based on a plurality of relevantreported aspects 14 associated with a plurality of source users 2* thatare determined to be relevant to achieving the one or more targetoutcomes. In some cases, the relevant reported aspects 14 may have beenoriginally reported via log entries such as microblog entries and/orstatus reports. A log entry may be any entry that indicates any aspectof, for example, a source user 2* that may be entered continuously,regularly, semi-regularly, randomly, or on a one-time basis.

In some cases, the computing device 10 may have previously received anumber of reported aspects 13 that include the relevant reported aspects14 (e.g., the reported aspects 13 may include both relevant reportedaspects 14 and non-relevant reported aspects). After receiving thereported aspects 13 including the relevant reported aspects 14, thereported aspects 13 including the relevant reported aspects 14 may bestored in a memory 116. In various embodiments, the reported aspects 13as well as the relevant reported aspects 14 may be obtained from avariety of sources including for example, one or more network servers60, local source user devices 20*, one or more sensor integrated devices40, and/or one or more third parties 6.

Alternatively, the plurality of relevant reported aspects 14 may beselectively acquired by the computing device 10 as a result of thecomputing device 10 transmitting one or more solicitations 12 thatsolicits for the relevant reported aspects 14. Such solicitations 12 maybe sent to a variety of network devices including, for example, to oneor more network servers 60, one or more sensor integrated devices 40,local source user devices 20*, and so forth. Note that in embodimentswhere the computing device 10 receives a plurality of reported aspects13 including a plurality of relevant reported aspects 14, the computingdevice 10 may, after receiving the plurality of reported aspects 13,store the reported aspects 13 (as well as the relevant reported aspects14 in a memory 116). After acquiring the relevant reported aspects 14, atemplate 16 may be developed based, at least in part, on theidentification of the relevant reported aspects 14 (associated withmultiple source users 2*) from a plurality of reported aspects 13. Insome cases, the template 16 may be developed by including into thetemplate 16 one or more emulatable aspects that are each developed basedon relevant reported aspects 14 of multiple source users 2*.

In embodiments where the template 16 includes a plurality of emulatableaspects the development of the template 16 may further include definingin the template 16 the relationships (e.g., temporal or specific timerelationships) between the plurality of emulatable aspects that may beincluded in the template 16. Such relationships may also be based, atleast in part, on the plurality of relevant reported aspects 14 of theplurality of source users 2*.

After developing the template 16, the template 16 may be presented to atleast one end user 4*, to one or more network servers 60, to one or morethird parties 6, or to one or more source users 2* via one or morecommunication networks 50. In embodiments in which the computing device10 is a local client device such as local end user device 30* or a localsource user device 20*, the template 16 may be presented via a userinterface 120.

In various embodiments, the computing device 10 may be a server (e.g.,one of the one or more network servers 60) that may be located at asingle network site, located across multiple network sites, or may be aconglomeration of servers located at multiple network sites. Inembodiments in which the computing device 10 is a source user device(e.g., local source user device 20*) or an end user device (e.g., localend user device 30*) rather than a network server 60, the computingdevice 10 may be any one of a wide range of mobile or stationarycomputing/communication devices including, for example, a laptop, adesktop, a workstation, a cellular telephone, a personal digitalassistant (PDA), a Smartphone, a web tablet such as a Netbook, and soforth.

Referring back to the exemplary environment 100 of FIGS. 1 a and 1 b, invarious embodiments the one or more sensor integrated devices 40 of theexemplary environment 100 of FIGS. 1 a and 1 b may directly communicatewith the one or more communication networks 50. Alternatively, the oneor more sensor integrated devices 40 may indirectly communicate with theone or more communication networks 50 via the one or more local sourceuser devices 20* (e.g., via, for example, a personal area network orPAN). In various alternative embodiments, a sensor integrated device 40may be a variety of functional devices that may comprise of one or moresensors 240 and that may be operated or used by a source user 2*.Examples of such devices include, for example, a transportation vehicle(e.g., automobile, a motorcycle, a boat, a plane, and so forth), anexercise machine (e.g., a treadmill), a household appliance (e.g.,television set), and so forth.

As will be further described herein, the one or more sensors 240, whichmay also be included in the local source user devices 20*, the one ormore local end user devices 30*, and/or the computing device 10, mayinclude any type of sensors 240 that can sense one or more aspects of asource user 2* or, in some cases, an end user 4*. Examples of suchsensors 240 include, for example, sensing devices that can sense variousphysical characteristics of a source user 2* or an end user 4* (e.g.,heart rate sensor or blood pressure sensor), sensing devices that cansense activities of a source user 2* or an end user 4* (e.g., apedometer, an accelerometer, and so forth), sensing devices that cansense environment conditions (e.g., air quality sensors), sensingdevices that can sense the location of a source user 2* or an end user4* (e.g., global positioning system or GPS), sensing devices that canprovide physiological data that may be processed in order to determineinferred mental states of source users 2* or end users 4*, and so forth.

Each of the one or more local source user devices 20* and the local enduser devices 30* (as well as the computing device 10 in embodiments inwhich the computing device 10 is an end user device or a source userdevice) may be any one of a variety of computing/communication devicesincluding, for example, a cellular phone, a personal digital assistant(PDA), a laptop, a desktop, or other types of computing/communicationdevices. In some embodiments, the one or more local source user devices20* and/or the local end user devices 30* (as well as the computingdevice 10 in some embodiments) may be a handheld device such as acellular telephone, a Smartphone, a Mobile Internet Device (MID), anUltra Mobile Personal Computer (UMPC), a convergent device such as apersonal digital assistant (PDA), and so forth. Alternatively, suchlocal client devices (e.g., local source user device 20* and/or localend user devices 30*) may be a laptop, a desktop, a workstation, a webtablet such as a Netbook, or other types of devices that may not be ahandheld device in various alternative implementations.

The computing device 10 as illustrated in FIG. 1 b may include one ormore modules, sub-modules, and various other components. As shown, thecomputing device 10 may include at least a relevant reported aspectproviding module 102 (which may further include one or more sub-modulesas illustrated in FIG. 2 a) and a template developing module 104 (whichmay also include one or more sub-modules as illustrated in FIG. 2 b).The relevant reported aspect providing module 102 may be particularlyconfigured to, among other things, provide a plurality of relevantreported aspects 14 associated with a plurality of source users 2* thatare relevant to achieving one or more target outcomes, the providing ofthe plurality of relevant reported aspects 14 being based, at least inpart, on relevancy of the plurality of relevant reported aspects 14 withrespect to the one or more target outcomes. In contrast, the templatedeveloping module 104 may be particularly configured to, among otherthings, develop a template 16 designed to facilitate one or more endusers 4* to achieve the one or more target outcomes when one or moreemulatable aspects included in the template 16 are emulated, thedevelopment of the template 16 being based, at least in part, on theproviding of the plurality of relevant reported aspects 14 associatedwith the plurality of source users 2*.

In various implementations, the computing device 10 may further includea template presenting module 106 and a memory 116. The templatepresenting module 106 may be particularly configured to present thetemplate 16 to, for example, one or more end users 4*, to one or morenetwork servers 60, or to one or more third parties 6. In someimplementations, the template presenting module 106 may further includea template transmitting module 150 (e.g., configured to transmit, viathe one or more communication networks 50, the template 16) and/or atemplate indicating module 152 (e.g., configured to indicate, via theuser interface 120, the template 16).

The memory 116, in various implementations, may store a plurality ofreported aspects 13 that are associated with the plurality of sourceusers 2*. Among the plurality of reported aspects 13 stored in memory116 may be a plurality of relevant reported aspects 14 that may bedetermined to be relevant to achieving the one or more target outcomesof the template 16 that is developed by the template developing module104. Other types of data may also be stored in the memory 116 in variousalternative implementations. For example, in various implementations,the memory 116 may store one or more of end user relevancy indications142 (e.g., one or more indications that indicate the types of reportedor emulatable aspects that one or more end users 4* have an interest inor believes are relevant to achieving one or more target outcomes), oneor more end user limitations 143 (e.g., limitations such as contextuallimitations, physical limitations, personal limitations, and so forth,associated with one or more end users 4* that prevent one or moreemulatable aspects of the template 16 from being emulated by the one ormore end users 4*), and/or one or more source user relevancy indications144 (e.g., one or more indications provided by one or more source users2* that indicate at least which types of reported aspects 13 arerelevant to achieving one or more target outcomes).

In some cases, the memory 116 may also include, for example, one or morethird party source relevancy indications 145 (e.g., one or moreindications provided by one or more third party sources such as one ormore third parties 6 that indicate at least which types of reportedaspects 13 are relevant to achieving one or more target outcomes),and/or one or more predefined time period indications 146 (e.g., one ormore indications that indicate at least one time period such as a timeincrement or window that may be used to determine whether, for example,a reported aspect 13 is relevant for achieving at least one targetoutcome only if the reported aspect 13 indicates an aspect that occurredwithin the at least one time period from an occurrence of the targetoutcome as successfully achieved by, for example, a source user 2*).

In some implementations, the memory 116 may store one or moreapplications 140 (e.g., a text messaging application, an instantmessaging application, an email application, a social networkingapplication, a voice recognition system, a Web 1.0 application, and/orWeb 2.0 application to facilitate in communicating via, for example, theWorld Wide Web). The memory 116 may comprise of one or more of a massstorage device, a read-only memory (ROM), a programmable read-onlymemory (PROM), an erasable programmable read-only memory (EPROM), acache memory such as random access memory (RAM), a flash memory, asynchronous random access memory (SRAM), a dynamic random access memory(DRAM), and/or other types of memory devices.

The computing device 10 may also include, in various implementations, anetwork interface 118 (e.g., a network interface card or NIC), a userinterface 120 (e.g., a display monitor, a touchscreen, a microphone, aspeaker, a mouse, and so forth), and/or one or more sensors 240 that aredesigned to measure or sense one or more user aspects. Examples ofsensors 240 include, for example, devices that are designed to senseuser activities such as pedometers and accelerometers, devices that aredesigned to sense physiological characteristics such as heart ratemonitors or blood glucose monitors, devices that are designed to senseenvironmental conditions such as devices for measuring air quality,devices that are designed to detect user location such as GPS, and soforth. In some cases, the presence or absence of some of these modulesand components of computing device 10 may depend on, for example,whether the computing device 10 is a server, an end user device, or asource user device. For example, if the computing device 10 is a server,then the computing device 10 may not include a user interface 120.

In various implementations, the computing device 10 may include a logentry receiving module 108 that is particularly configured to receivelog entries associated with a plurality of source users 2*. In someimplementations, the log entry receiving module 108 may further includeone or more additional sub-modules. For example, in some instances, thelog entry receiving module 108 may include a social networking entryreceiving module 110 that is configured to receive social networkingentries (e.g., log entries provided through social networking channelssuch as social networking sites). The social networking entry receivingmodule 110 may further include a blog entry receiving module 111 (e.g.,configured to receive blog entries) and/or a status report receivingmodule 112 (e.g., configured to receive social networking statusreports). In the same or different implementations, the log entryreceiving module 108 may further include a journal entry receivingmodule 114 (e.g., configured to receive journal or diary entries) and/orsensor entry receiving module 115 (e.g., configured to receive logentries provided by sensors 240).

FIG. 2 a illustrates particular implementations of the relevant reportedaspect providing module 102 of FIG. 1 b. The relevant reported aspectproviding module 102 in various implementations may include, among otherthings, a memory acquiring module 202 that is configured to, among otherthings, acquire one or more of the plurality of relevant reportedaspects 14 that are relevant to achieving one or more target outcomesfrom a memory 116 and/or a network acquiring module 204 that isconfigured to acquire one or more of the plurality of relevant reportedaspects 14 via one or more communication networks 50 and that mayinclude a solicitation transmitting module 206 that is configured totransmit one or more solicitations 12 for the one or more relevantreported aspects 14 via the one or more communication networks 50.

In the same or different implementations, the relevant reported aspectproviding module 102 may include a “target outcome correspondingreported aspect” identifying module 208, a source user identifyingmodule 210, an identified source user associated reported aspectproviding module 212, and/or a “relevancy factor relevant reportedaspect” providing module 214. A more detailed discussion regarding thesesub-modules of the relevant reported aspect providing module 102 will beprovided with respect to the processes and operations to be describedherein.

FIG. 2 b illustrates particular implementations of the templatedeveloping module 104 of the computing device 10 of FIG. 1 b. In variousimplementations, the template developing module 104 may include at leastan emulatable aspect including module 216 that may be particularlyconfigured to include into a template 16 one or more emulatable aspects.Each of the one or more emulatable aspects to be included in thetemplate 16 by the emulatable aspect including module 216 may have beendeveloped based on a plurality of relevant reported aspects 14 of aplurality of source users 2*. The emulatable aspect including module 216may further include an emulatable aspect deriving module 218 that may beparticularly configured to derive the one or more emulatable aspects tobe included in the template 16. The emulatable aspect deriving module218 may, in turn, further include a commonly reported aspect determiningmodule 220, a deviation determining module 222 (which may furtherinclude a mean value determining module 224 and/or an average valuedetermining module 226), a compliant determining module 228, and/or aplausible emulatable aspect determining module 230. These modules andsub-modules of the template developing module 104 will be discussed ingreater detail below with respect to the processes and operation to bedescribed herein.

In some implementations, the template developing module 104 may furtherinclude an emulatable aspect relationship defining module 232 that isconfigured to define one or more relationships (e.g., temporal orspecific time relationships) between emulatable aspects in a template 16when the template 16 includes a plurality of emulatable aspects. Suchrelationships may be based, at least in part, on the relevant reportedaspects 14 provided by the relevant reported aspect providing module102. In some cases, such relationships may also be provided by usingtechniques similar to the techniques that will be described herein thatmay be used in order to derive the emulatable aspects to be included inthe template 16. In other cases, such relationships may be determined bydetermining trends that may be detected with respect to how relevantreported aspects 14 were executed by the source users 2*. In still othercases, more sophisticated analysis may be performed in order todetermine the relationships between the emulatable aspects that may beincluded in a template 16.

Referring back to the computing device 10 of FIG. 1 b, the variousmodules (e.g., the relevant reported aspect providing module 102, thetemplate developing module 104, and so forth) along with theirsub-modules included in the computing device 10 may be implemented usinghardware, software, firmware, or any combination thereof. For example,in some implementations, the relevant reported aspect providing module102 and/or the template developing module 104 may be implemented with aprocessor 802 (e.g., microprocessor, controller, and so forth) executingcomputer readable instructions 804 (e.g., computer program product)stored in a storage medium 806 (e.g., volatile or non-volatile memory)such as a signal-bearing medium as depicted in the computing device 10of FIG. 8. Alternatively, hardware such as application specificintegrated circuit (ASIC) may be employed in order to implement suchmodules in some alternative implementations.

A more detailed description of the computing device 10 of FIG. 1 b andits components will now be provided with respect to the processes andoperations to be described herein. FIG. 3 illustrates an operationalflow 300 representing example operations directed to, among otherthings, development of a template 16 that is designed to facilitate oneor more end users 4* to achieve the one or more target outcomes when oneor more emulatable aspects included in the template 16 are emulated, thedevelopment of the template 16 being based, at least in part, onrelevant reported aspects 14 of a plurality of source users 2* that arerelevant to achieving the one or more target outcomes.

In FIG. 3 and in the following figures that include various examples ofoperational flows, discussions and explanations of the operational flowswill be provided with respect to the exemplary environment 100 describedabove as illustrated in FIGS. 1 a and 1 b, and/or with respect to otherexamples (e.g., as provided in FIGS. 2 a and 2 b) and contexts. However,it should be understood that the operational flows may be executed in anumber of other environments and contexts, and/or in modified versionsof FIGS. 1 a, 1 b, 2 a, and 2 b. Also, although the various operationalflows are presented in the sequence(s) illustrated, it should beunderstood that the various operations may be performed in other ordersother than those which are illustrated, or may be performedconcurrently.

Further, in FIG. 3 and in the figures to follow thereafter, variousoperations may be depicted in a box-within-a-box manner. Such depictionsmay indicate that an operation in an internal box may comprise anoptional example embodiment of the operational step illustrated in oneor more external boxes. However, it should be understood that internalbox operations may be viewed as independent operations separate from anyassociated external boxes and may be performed in any sequence withrespect to all other illustrated operations, or may be performedconcurrently.

In any event, after a start operation, the operational flow 300 may moveto a relevant reported aspect providing operation 302 for providing aplurality of relevant reported aspects associated with a plurality ofsource users that are relevant to achieving one or more target outcomes,the providing of the plurality of relevant reported aspects being based,at least in part, on relevancy of the plurality of relevant reportedaspects with respect to the one or more target outcomes. For instance,and as an illustration, the relevant reported aspect providing module102 of the computing device 10 of FIG. 1 b providing (e.g., acquiring,retrieving, identifying, finding, locating, accessing, and so forth) aplurality of relevant reported aspects 14 associated with a plurality ofsource users 2* that are relevant to achieving one or more targetoutcomes (e.g., health or medical outcomes, athletic or fitnessoutcomes, user state outcomes such as subjective mental state outcomes,spiritual outcomes, and so forth), the providing of the plurality ofrelevant reported aspects 14 being based, at least in part, on relevancyof the plurality of relevant reported aspects 14 with respect to the oneor more target outcomes.

In addition to the relevant reported aspect providing operation 302,operational flow 300 may also include a template developing operation304 for developing a template designed to facilitate one or more endusers to achieve the one or more target outcomes when one or moreemulatable aspects included in the template are emulated, thedevelopment of the template being based, at least in part, on theproviding of the plurality of relevant reported aspects associated withthe plurality of source users. For instance, the template developingmodule 104 of the computing device 10 developing a template 16 that isdesigned to facilitate one or more end users 4* to achieve the one ormore target outcomes when one or more emulatable aspects included in thetemplate 16 are emulated, the development of the template 16 beingbased, at least in part, on the providing of the plurality of relevantreported aspects 14 associated with the plurality of source users 2*.Note that in various implementations, the relevant reported aspectproviding operation 302 and the template developing operation 304 ofFIG. 3 may be implemented in a variety of different ways.

For example, FIGS. 4 a, 4 b, 4 c, 4 d, and 4 e illustrate various waysthat the relevant reported aspect providing operation 302 of FIG. 3 maybe executed in various alternative implementations. For instance, therelevant reported aspects 14 provided through operation 302 may beprovided from various sources in various alternative implementations. Insome implementations, for example, the relevant reported aspectproviding operation 302 may include an operation 402 for acquiring therelevant reported aspects from a memory as depicted in FIG. 4 a. Forinstance, the memory acquiring module 202 (see FIG. 2 a) of thecomputing device 10 acquiring (e.g., locating, finding, retrieving,identifying, and so forth) the relevant reported aspects 14 from amemory 116 (e.g., volatile or non-volatile memory including, forexample, cache memory).

In some implementations, the relevant reported aspect providingoperation 302 may include an operation 403 for acquiring the relevantreported aspects via one or more communication networks as depicted inFIG. 4 a. For instance, the network acquiring module 204 (see FIG. 2 a)of the computing device 10 acquiring (e.g., soliciting, querying,retrieving, receiving, and so forth) the relevant reported aspects 14via one or more communication networks 50 (e.g., a wireless networkand/or a wired network).

In some cases, operation 403 may, in turn, include an operation 404 foracquiring the relevant reported aspects via the one or morecommunication networks by transmitting one or more solicitations for theone or more relevant reported aspects via the one or more communicationnetworks as depicted in FIG. 4 a. For instance, the network acquiringmodule 204 of the computing device 10 acquiring the relevant reportedaspects 14 via the one or more communication networks 50 by having thesolicitation transmitting module 206 (see FIG. 2 a) transmitting one ormore solicitations 12 (e.g., requests, queries, and so forth) for theone or more relevant reported aspects 14 via the one or morecommunication networks 50.

In the same or different implementations, the relevant reported aspectproviding operation 302 of FIG. 3 may include one or more operations todetermine or identify the plurality of relevant reported aspects 14. Forexample, in some implementations, the relevant reported aspect providingoperation 302 of FIG. 3 may include an operation 405 for providing theplurality of relevant reported aspects by at least identifying reportedaspects that correspond to the one or more target outcomes as depictedin FIG. 4 b. For instance, the relevant reported aspect providing module102 including the “target outcome corresponding reported aspectidentifying” module 208 of the computing device 10 providing theplurality of relevant reported aspects 14 by at least identifyingreported aspects 13 (which may be stored in a memory 116 and/or locatedat one or more network sites such as at the one or more local sourceuser devices 20* or at the one or more network servers 60) thatcorrespond (e.g., equivalent or substantially equivalent) to the one ormore target outcomes.

Operation 405, in turn, may further include one or more additionaloperations in various alternative implementations. For example, in someimplementations, operation 405 may include an operation 406 foridentifying the source users based on the source users association withthe reported aspects that corresponds to the one or more target outcomesas depicted in FIG. 4 b. For instance, the source user identifyingmodule 210 (see FIG. 2 a) of the computing device 10 identifying thesource users 2* based on the source users 2*association with thereported aspects (e.g., source users 2* reporting that they had achievedan A1C score, an indication of blood glucose level, of 6.2 or 6.0) thatcorresponds to the one or more target outcomes (e.g., A1C score of 6.2or lower).

In some implementations, operation 406 may further include an operation407 for providing reported aspects that are at least associated with theidentified source users as depicted in FIG. 4 b. For instance, the“identified source user associated reported aspect providing” module 212(see FIG. 2 a) of the computing device 10 providing reported aspects 13that are at least associated with the identified source users 2*. Inother words, providing reported aspects 13 that indicate specificaspects of the identified source users 2*.

In some implementations, operation 407 may further include an operation408 for providing, from the reported aspects that are at leastassociated with the identified source users, reported aspects that arerelevant with respect to one or more relevancy factors as depicted inFIG. 4 b. For instance, the relevancy factor relevant reported aspectproviding module 214 (see FIG. 2 a) of the computing device 10providing, from the reported aspects 13 that are at least associatedwith the identified source users 2*, reported aspects 13 (e.g., relevantreported aspects 14) that are relevant with respect to one or morerelevancy factors.

In various implementations, operation 408 may further include one ormore additional operations including, for example, an operation 409 forproviding the reported aspects that are relevant with respect to the oneor more relevancy factors by providing reported aspects that are atleast associated with the identified source users and that belong to oneor more aspect types that are of interest to one or more end users asdepicted in FIG. 4 b. For instance, the relevancy factor relevantreported aspect providing module 214 of the computing device 10providing the reported aspects 13 that are relevant with respect to theone or more relevancy factors by providing reported aspects 13 (e.g.,relevant reported aspects 14) that are at least associated with theidentified source users 2* and that belong to one or more aspect typesthat are of interest to one or more end users 4*.

In the same or different implementations, operation 408 may include anoperation 410 for providing the reported aspects that are relevant withrespect to the one or more relevancy factors by providing reportedaspects that are at least associated with the identified source usersand that belong to one or more aspect types that have been indicated byat least one source user as being relevant to the achievement of the oneor more target outcomes as depicted in FIG. 4 b. For instance, therelevancy factor relevant reported aspect providing module 214 of thecomputing device 10 providing the reported aspects 13 that are relevantwith respect to the one or more relevancy factors by providing reportedaspects 13 (e.g., relevant reported aspects 14) that are at leastassociated with the identified source users 2* and that belong to one ormore aspect types that have been indicated by at least one source user2* as being relevant to the achievement of the one or more targetoutcomes.

In the same or different implementations, operation 408 may include anoperation 411 for providing the reported aspects that are relevant withrespect to the one or more relevancy factors by providing reportedaspects that are at least associated with the identified source usersand that belong to one or more aspect types that have been indicated byat least one third party source as being relevant to the achievement ofthe one or more target outcomes as depicted in FIG. 4 b. For instance,the relevancy factor relevant reported aspect providing module 214 ofthe computing device 10 providing the reported aspects 13 that arerelevant with respect to the one or more relevancy factors by providingreported aspects 13 (e.g., relevant reported aspects 14) that are atleast associated with the identified source users 2* and that belong toone or more aspect types that have been indicated by at least one thirdparty source (e.g., a publication, a peer-reviewed research publication,a third party 6, and so forth) as being relevant to the achievement ofthe one or more target outcomes.

In the same or different implementations, operation 408 may include anoperation 412 for providing the reported aspects that are relevant withrespect to the one or more relevancy factors by providing reportedaspects that are at least associated with the identified source usersand that indicate aspects of the identified source users that occurredwithin one or more predefined time periods, respectively, fromoccurrences of the reported aspects that were identified ascorresponding to the one or more target outcomes as depicted in FIG. 4b. For instance, the relevancy factor relevant reported aspect providingmodule 214 of the computing device 10 providing the reported aspects 13that are relevant with respect to the one or more relevancy factors byproviding reported aspects 13 (e.g., cease consuming caffeine andincrease exercise activities) that are at least associated with theidentified source users 2* and that indicate aspects of the identifiedsource users 2* that occurred within one or more predefined time periods(e.g., two months), respectively, from occurrences of the reportedaspects 13 (e.g., lowering blood pressure) that were identified ascorresponding to the one or more target outcomes (e.g., lowering bloodpressure). The purpose here is to, for example, exclude fromconsideration those reported aspects 13 that indicate aspects of theidentified source users 2* that occurred well before or well after theachievement of the one or more target outcomes by the identified sourceuser 2*. In various implementations, the predefined time periods may beset by a source user 2*, by an end user 4*, or by a third party 6 (e.g.,a physician, a content provider, a network service provider, and soforth).

In various implementations, operation 412 may include an operation 413for providing the reported aspects that are relevant with respect to theone or more relevancy factors by providing reported aspects that are atleast associated with the identified source users and that indicateaspects of the identified source users that occurred prior to and withinone or more predefined time periods, respectively, from occurrences ofthe reported aspects that were identified as corresponding to the one ormore target outcomes as depicted in FIG. 4 b. For instance, therelevancy factor relevant reported aspect providing module 214 of thecomputing device 10 providing the reported aspects 13 that are relevantwith respect to the one or more relevancy factors by providing reportedaspects 13 (e.g., jogging) that are at least associated with theidentified source users 2* and that indicate aspects of the identifiedsource users 2* that occurred prior to and within one or more predefinedtime periods (e.g., 2 weeks), respectively, from occurrences of thereported aspects 13 (e.g., getting 8 hours of continuous and restfulsleep) that were identified as corresponding to the one or more targetoutcomes (e.g., 8 hours of continuous and restful sleep).

The plurality of relevant reported aspects 14 that may be providedthrough the relevant reported aspect providing operation 302 of FIG. 3may have been originally reported by a variety of different ways. Forexample, in some implementations, the relevant reported aspect providingoperation 302 of FIG. 3 may include an operation 414 for providing theplurality of relevant reported aspects associated with the plurality ofsource users that are relevant to achieving one or more target outcomesincluding one or more relevant reported aspects that were at leastoriginally reported via one or more log entries as depicted in FIG. 4 c.For instance, the relevant reported aspect providing module 102 of thecomputing device 10 providing the plurality of relevant reported aspects14 associated with the plurality of source users 2* that are relevant toachieving one or more target outcomes including one or more relevantreported aspects 14 that were at least originally reported via one ormore log entries (e.g., as received by, for example, the log entryreceiving module 108 of the computing device 10).

In various implementations, operation 414 may include one or moreadditional operations. For example, in some cases, operation 414 mayfurther include an operation 415 for providing the plurality of relevantreported aspects associated with the plurality of source users that arerelevant to achieving one or more target outcomes including one or morerelevant reported aspects that were at least originally reported via oneor more social networking entries as depicted in FIG. 4 c. For instance,the relevant reported aspect providing module 102 of the computingdevice 10 providing the plurality of relevant reported aspects 14associated with the plurality of source users 2* that are relevant toachieving one or more target outcomes including one or more relevantreported aspects 14 that were at least originally reported via one ormore social networking entries (e.g., as received by, for example, thesocial networking entry receiving module 110 of the computing device10).

In various implementations, operation 415 may further include anoperation 416 for providing the plurality of relevant reported aspectsassociated with the plurality of source users that are relevant toachieving one or more target outcomes including one or more relevantreported aspects that were at least originally reported via one or moreblog entries as depicted in FIG. 4 c. For instance, the relevantreported aspect providing module 102 of the computing device 10providing the plurality of relevant reported aspects 14 associated withthe plurality of source users 2* that are relevant to achieving one ormore target outcomes including one or more relevant reported aspects 14that were at least originally reported via one or more blog entries suchas one or more microblog entries (e.g., as received by, for example, theblog entry receiving module 111 of the computing device 10).

In the same or different implementations, operation 415 may include anoperation 417 for providing the plurality of relevant reported aspectsassociated with the plurality of source users that are relevant toachieving one or more target outcomes including one or more relevantreported aspects that were at least originally reported via one or morestatus reports as depicted in FIG. 4 c. For instance, the relevantreported aspect providing module 102 of the computing device 10providing the plurality of relevant reported aspects 14 associated withthe plurality of source users 2* that are relevant to achieving one ormore target outcomes including one or more relevant reported aspects 14that were at least originally reported via one or more status reportssuch as one or more social networking status reports (e.g., as receivedby, for example, the status report receiving module 112 of the computingdevice 10).

In some implementations, operation 414 may include an operation 418 forproviding the plurality of relevant reported aspects associated with theplurality of source users that are relevant to achieving one or moretarget outcomes including one or more relevant reported aspects thatwere at least originally reported via one or more journal entries asdepicted in FIG. 4 c. For instance, the relevant reported aspectproviding module 102 of the computing device 10 providing the pluralityof relevant reported aspects 14 associated with the plurality of sourceusers 2* that are relevant to achieving one or more target outcomesincluding one or more relevant reported aspects 14 that were at leastoriginally reported via one or more journal entries (e.g., as receivedby, for example, the journal entry receiving module 114 of the computingdevice 10).

In the same or different implementations, operation 414 may include anoperation 419 for providing the plurality of relevant reported aspectsassociated with the plurality of source users that are relevant toachieving one or more target outcomes including one or more relevantreported aspects that were at least originally reported by one or moreof the source users as depicted in FIG. 4 c. For instance, the relevantreported aspect providing module 102 of the computing device 10providing the plurality of relevant reported aspects 14 associated withthe plurality of source users 2* that are relevant to achieving one ormore target outcomes including one or more relevant reported aspects 14that were at least originally reported by one or more of the sourceusers 2*.

In the same or different implementations, operation 414 may furtherinclude an operation 420 for providing the plurality of relevantreported aspects associated with the plurality of source users that arerelevant to achieving one or more target outcomes including one or morerelevant reported aspects that were at least originally reported by oneor more third parties as depicted in FIG. 4 c. For instance, therelevant reported aspect providing module 102 of the computing device 10providing the plurality of relevant reported aspects 14 associated withthe plurality of source users 2* that are relevant to achieving one ormore target outcomes including one or more relevant reported aspects 14that were at least originally reported by one or more third parties 6.

In some implementations, operation 414 may include an operation 421 forproviding the plurality of relevant reported aspects associated with theplurality of source users that are relevant to achieving one or moretarget outcomes including one or more relevant reported aspects thatwere at least originally reported by one or more sensors as depicted inFIG. 4 c. For instance, the relevant reported aspect providing module102 of the computing device 10 providing the plurality of relevantreported aspects 14 associated with the plurality of source users 2*that are relevant to achieving one or more target outcomes including oneor more relevant reported aspects 14 that were at least originallyreported by one or more sensors 240 (which may be located at one or morelocal source user devices 20*, at one or more sensor integrated devices40, and/or at the computing device 10).

In various implementations, the relevant reported aspect providingoperation 302 of FIG. 3 may include an operation 422 for providing theplurality of relevant reported aspects including providing a first oneor more reported aspects that are associated with a first source userand that are relevant to achieving at least one of the one or moretarget outcomes and providing a second one or more reported aspects thatare associated with a second source user and that are relevant toachieving the at least one of the one or more target outcomes, theproviding of the first one or more reported aspects and the second oneor more reported aspects being based on the first one or more reportedaspects' and the second one or more reported aspects' relevancy withrespect to the at least one of the one or more target outcomes asdepicted in FIG. 4 d. For instance, the relevant reported aspectproviding module 102 of the computing device 10 providing the pluralityof relevant reported aspects 14 including providing a first one or morereported aspects 13 that are associated with a first source user 2 a andthat are relevant to achieving at least one of the one or more targetoutcomes and providing a second one or more reported aspects 13 that areassociated with a second source user 2 b and that are relevant toachieving the at least one of the one or more target outcomes, theproviding of the first one or more reported aspects 13 and the secondone or more reported aspects 13 being based on relevancy of the firstone or more reported aspects 13 and the second one or more reportedaspects 13 with respect to the at least one of the one or more targetoutcomes.

The plurality of relevant reported aspects 14 that may be providedthrough the relevant reported aspect providing operation 302 of FIG. 3may include a variety of aspects related to the plurality of sourceusers 2*. For example, in some implementations, relevant reported aspectproviding operation 302 may include an operation 423 for providing theplurality of relevant reported aspects including providing a pluralityof relevant reported aspects related to a plurality of behaviorincidences associated with the plurality of source users as depicted inFIG. 4 d. For instance, the relevant reported aspect providing module102 of the computing device 10 providing the plurality of relevantreported aspects 14 including providing a plurality of relevant reportedaspects 14 related to a plurality of behavior incidences (e.g., dietaryactivities, exercise activities, social behavior, and so forth)associated with the plurality of source users 2*.

In some implementations, operation 423 may further include an operation424 for providing the plurality of relevant reported aspects includingproviding a plurality of relevant reported aspects related to aplurality of incidences of user activities associated with the pluralityof source users as depicted in FIG. 4 d. For instance, the relevantreported aspect providing module 102 of the computing device 10providing the plurality of relevant reported aspects 14 includingproviding a plurality of relevant reported aspects 14 related to aplurality of incidences of user activities (e.g., consuming a particularmedication or food, sleeping in a particular type of bed, reading aparticular book, and so forth) associated with the plurality of sourceusers 2*.

In the same or different implementations, operation 423 may include anoperation 425 for providing the plurality of relevant reported aspectsincluding providing a plurality of relevant reported aspects related toa plurality of incidences of user attitudes associated with theplurality of source users as depicted in FIG. 4 d. For instance, therelevant reported aspect providing module 102 of the computing device 10providing the plurality of relevant reported aspects 14 includingproviding a plurality of relevant reported aspects 14 related to aplurality of incidences of user attitudes (e.g., disdain, loving orcaring, and so forth) associated with the plurality of source users 2*.

In the same or different implementations, operation 423 may include anoperation 426 for providing the plurality of relevant reported aspectsincluding providing a plurality of relevant reported aspects related toa plurality of incidences of user conduct associated with the pluralityof source users as depicted in FIG. 4 d. For instance, the relevantreported aspect providing module 102 of the computing device 10providing the plurality of relevant reported aspects 14 includingproviding a plurality of relevant reported aspects 14 related to aplurality of incidences of user conduct (e.g., treating subordinates asequal, driving a friend's car carefully, and so forth) associated withthe plurality of source users 2*.

In some implementations, the relevant reported aspect providingoperation 302 of FIG. 3 may include an operation 427 for providing theplurality of relevant reported aspects including providing a pluralityof relevant reported aspects related to a plurality of incidences ofuser beliefs associated with the plurality of source users as depictedin FIG. 4 e. For instance, the relevant reported aspect providing module102 of the computing device 10 providing the plurality of relevantreported aspects 14 including providing a plurality of relevant reportedaspects 14 related to a plurality of incidences of user beliefs (e.g.,dietary beliefs, social or religious beliefs, superstitious beliefs, andso forth) associated with the plurality of source users 2*.

In the same or different implementations, the relevant reported aspectproviding operation 302 may include an operation 428 for providing theplurality of relevant reported aspects including providing a pluralityof relevant reported aspects related to a plurality of incidences ofuser states associated with the plurality of source users as depicted inFIG. 4 e. For instance, the relevant reported aspect providing module102 of the computing device 10 providing the plurality of relevantreported aspects 14 including providing a plurality of relevant reportedaspects 14 related to a plurality of incidences of user states (e.g.,marital state, academic state, social state, health or fitness state,mental state, physical state, and so forth) associated with theplurality of source users 2*.

In the same or different implementations, the relevant reported aspectproviding operation 302 may include an operation 429 for providing theplurality of relevant reported aspects including providing a pluralityof relevant reported aspects related to a plurality of incidences ofuser physical characteristics associated with the plurality of sourceusers as depicted in FIG. 4 e. For instance, the relevant reportedaspect providing module 102 of the computing device 10 providing theplurality of relevant reported aspects 14 including providing aplurality of relevant reported aspects 14 related to a plurality ofincidences of user physical characteristics (e.g., body fat level, haircolor, and so forth) associated with the plurality of source users 2*.

In the same or different implementations, the relevant reported aspectproviding operation 302 may include an operation 430 for providing theplurality of relevant reported aspects including providing a pluralityof relevant reported aspects related to a plurality of incidences ofuser locations associated with the plurality of source users as depictedin FIG. 4 e. For instance, the relevant reported aspect providing module102 of the computing device 10 providing the plurality of relevantreported aspects 14 including providing a plurality of relevant reportedaspects 14 related to a plurality of incidences of user locationsassociated with the plurality of source users 2*.

In the same or different implementations, the relevant reported aspectproviding operation 302 may include an operation 431 for providing theplurality of relevant reported aspects including providing a pluralityof relevant reported aspects related to a plurality of incidences ofexternal events associated with the plurality of source users asdepicted in FIG. 4 e. For instance, the relevant reported aspectproviding module 102 of the computing device 10 providing the pluralityof relevant reported aspects 14 including providing a plurality ofrelevant reported aspects 14 related to a plurality of incidences ofexternal events (e.g., external environmental or atmospheric conditions)associated with the plurality of source users 2*.

Referring back to FIG. 3, the template developing operation 304 may beimplemented in a number of different ways in various alternativeimplementations. For example, in some implementations, the templatedeveloping operation 304 may include an operation 532 for developing thetemplate by including into the template one or more emulatable aspectsthat were derived based, at least in part, on the plurality of relevantreported aspects that are associated with the plurality of source usersand that are relevant to achieving the one or more target outcomes asdepicted in FIG. 5 a. For instance, the template developing module 104of the computing device 10 developing the template 16 by having theemulatable aspect including module 216 (see FIG. 2 b) include into thetemplate 16 one or more emulatable aspects that were derived (e.g., asderived by, for example, the emulatable aspect deriving module 218)based, at least in part, on the plurality of relevant reported aspects14 that are associated with the plurality of source users 2* and thatare relevant to achieving one or more target outcomes.

In various implementations, operation 532 may further include anoperation 533 for developing the template by including into the templateat least one emulatable aspect that was derived based, at least in part,on a plurality of relevant reported aspects that are each associatedwith different source users as depicted in FIG. 5 a. For instance, thetemplate developing module 104 of the computing device 10 developing thetemplate 16 by having the emulatable aspect including module 216 includeinto the template 16 at least one emulatable aspect that was derived(e.g., as derived by, for example, the emulatable aspect deriving module218) based, at least in part, on a plurality of relevant reportedaspects 14 that are each associated with different source users 2*.

In some cases, operation 533 may further include an operation 534 fordeveloping the template by including into the template at least oneemulatable aspect that was derived based, at least in part, on a firstrelevant reported aspect that is associated with a first source user anda second relevant reported aspect that is associated with a secondsource user as depicted in FIG. 5 a. For instance, the templatedeveloping module 104 of the computing device 10 developing the template16 by having the emulatable aspect including module 216 (see FIG. 2 b)include into the template 16 at least one emulatable aspect (e.g.,jogging for 45 minutes) that was derived (e.g., as derived by, forexample, the emulatable aspect deriving module 218) based, at least inpart, on a first relevant reported aspect (e.g., jogging for 55 minutes)that is associated with a first source user 2 a and a second relevantreported aspect (e.g., jogging for 35 minutes) that is associated with asecond source user 2 b.

In some implementations, operation 534 may further include one or moreadditional operations including, for example, an operation 535 fordeveloping the template by including into the template a secondemulatable aspect that was derived based, at least in part, on a thirdrelevant reported aspect that is associated with the first source userand a fourth relevant reported aspect that is associated with the secondsource user as depicted in FIG. 5 a. For instance, the templatedeveloping module 104 of the computing device 10 developing the template16 by having the emulatable aspect including module 216 include into thetemplate 16 a second emulatable aspect (e.g., jogging at a moderatepace) that was derived (e.g., as derived by, for example, the emulatableaspect deriving module 218) based, at least in part, on a third relevantreported aspect (e.g., jogging at a very quick pace) that is associatedwith the first source user 2 a and a fourth relevant reported aspect(e.g., jogging at a very slow pace) that is associated with the secondsource user 2 b.

In the same or different implementations, operation 534 may include anoperation 536 for developing the template by including into the templatea second emulatable aspect that was derived based, at least in part, ona third relevant reported aspect that is associated with a third sourceuser and a fourth relevant reported aspect that is associated with afourth source user as depicted in FIG. 5 a. For instance, the templatedeveloping module 104 of the computing device 10 developing the template16 by having the emulatable aspect including module 216 include into thetemplate 16 a second emulatable aspect (e.g., rowing for one hour) thatwas derived (e.g., as derived by, for example, the emulatable aspectderiving module 218) based, at least in part, on a third relevantreported aspect (e.g., rowing for one hour) that is associated with athird source user 2 c and a fourth relevant reported aspect (e.g.,swimming for one hour) that is associated with a fourth source user 2 d.

Note that in this example, the second emulatable aspect that wasincluded into the template 16 was the same as the third relevantreported aspect (of the third source user 2 c) completely different fromthe fourth relevant reported aspect (of the fourth source user 2 d). Incases like this, certain factors or rules may be considered in resolvingconflicts between relevant reported aspects in order to, for example,determine the second emulatable aspect. For example, there may be a rulethat says that the most commonly executed reported aspect be used inorder to determine an emulatable aspect (e.g., in the above example, thefirst source user 2 a and the second source user 2 b may also havereported rowing for one hour). In another example, relevant reportedaspects of, for example, a first group of source users 2* may be givenmore weight than the relevant reported aspects of a second group ofsource users 2* because the first group of source users 2* may havesimilar traits (e.g., physical traits, health traits, intellectualtraits, and so forth) as the end users 4*. Of course, those skilled inthe art will recognize that there are many other tie breaker rules thatmay be used in order to resolve conflicts between relevant reportedaspects.

In various implementations, operation 533 for developing a template 16by including into the template 16 at least one emulatable aspect mayinclude an operation 537 for developing the template by including intothe template at least one emulatable aspect that corresponds to acommonly reported aspect that is determined to be associated with two ormore of the plurality of source users as depicted in FIG. 5 a. Forinstance, the template developing module 104 of the computing device 10developing the template 16 by having the emulatable aspect includingmodule 216 include into the template 16 at least one emulatable aspectthat corresponds to a commonly reported aspect (e.g., a source useraspect that is reported by, for example, more than one source user 2*)that is determined to be associated with two or more of the plurality ofsource users 2* (e.g., as determined by the commonly reported aspectdetermining module 220).

In some implementations, operation 537 may further include an operation538 for developing the template by including into the template at leastone emulatable aspect that corresponds to a commonly reported aspectthat is determined to be associated with a majority of the plurality ofsource users as depicted in FIG. 5 a. For instance, the templatedeveloping module 104 of the computing device 10 developing the template16 by having the emulatable aspect including module 216 include into thetemplate 16 at least one emulatable aspect that corresponds to acommonly reported aspect that is determined to be associated with amajority of the plurality of source users 2* (e.g., as determined by thecommonly reported aspect determining module 220).

In various implementations, the operation 533 for developing a template16 by including into the template 16 at least one emulatable aspect mayinclude an operation 539 for developing the template by including intothe template at least one emulatable aspect that includes at least aportion that was derived based, at least in part, on deviations of theplurality of relevant reported aspects with respect to each other asdepicted in FIG. 5 b. For instance, the template developing module 104of the computing device 10 developing the template 16 by having theemulatable aspect including module 216 include into the template 16 atleast one emulatable aspect (e.g., swimming for 30 minutes) thatincludes at least a portion (e.g., 30 minutes) that was derived based,at least in part, on deviations of the plurality of relevant reportedaspects 14 with respect to each other (e.g., as determined by, forexample, the deviation determining module 222).

In some implementations, operation 539 may further include an operation540 for developing the template by including into the template at leastone mean value emulatable aspect that was at least partially developedby determining a mean value for the plurality of relevant reportedaspects as depicted in FIG. 5 b. For instance, the template developingmodule 104 of the computing device 10 developing the template 16 byhaving the emulatable aspect including module 216 include into thetemplate 16 at least one mean value emulatable aspect that was at leastpartially developed by determining a mean value for the plurality ofrelevant reported aspects 14 (e.g., as determined by, for example, themean value determining module 224). For example, in the above swimmingexample, determining the mean value for the amount of time that thesource users 2* reported swimming. Note that in some cases it may alsobe possible to obtain a mean value for variables that may not beconsidered quantifiable variables such as, for example, “jogging” (e.g.,a mean value can be obtained from, for example, jogging at a fast pace,jogging at a moderate pace, or jogging at a slow pace).

In the same or different implementations, operation 539 may include anoperation 541 for developing the template by including into the templateat least one average value emulatable aspect that was at least partiallydeveloped by determining an average value for the plurality of relevantreported aspects as depicted in FIG. 5 b. For instance, the templatedeveloping module 104 of the computing device 10 developing the template16 by having the emulatable aspect including module 216 include into thetemplate 16 at least one average value emulatable aspect that was atleast partially developed by determining an average value for theplurality of relevant reported aspects 14 (e.g., as determined by, forexample, the average value determining module 226).

In some cases, operation 533 for developing a template 16 by includinginto the template 16 at least one emulatable aspect may include anoperation 542 for developing the template by including into the templateat least one emulatable aspect that was derived based, at least in part,on the plurality of relevant reported aspects that are each associatedwith a different source user, the at least one emulatable aspect beingdetermined to be compliant with one or more limitations associated withat least one of the one or more end users as depicted in FIG. 5 b. Forinstance, the template developing module 104 of the computing device 10developing the template 16 by having the emulatable aspect includingmodule 216 include into the template 16 at least one emulatable aspectthat was derived by the emulatable aspect deriving module 218 based, atleast in part, on the plurality of relevant reported aspects 14* thatare each associated with a different source user 2*, the at least oneemulatable aspect being determined (e.g., as determined by the compliantdetermining module 228) to be compliant with (e.g., not violating) oneor more limitations associated with at least one of the one or more endusers 4*.

In some implementations, operation 542 may further include an operation543 for developing the template by including into the template at leastone emulatable aspect that was derived based, at least in part, on theplurality of relevant reported aspects that are each associated with adifferent source user, the at least one emulatable aspect beingdetermined to be compliant with one or more contextual limitationsassociated with at least one of the one or more end users as depicted inFIG. 5 b. For instance, the template developing module 104 of thecomputing device 10 developing the template 16 by having the emulatableaspect including module 216 include into the template 16 at least oneemulatable aspect that was derived by the emulatable aspect derivingmodule 218 based, at least in part, on the plurality of relevantreported aspects 14* that are each associated with a different sourceuser 2*, the at least one emulatable aspect being determined (e.g., asdetermined by the compliant determining module 228) to be compliant withone or more contextual limitations (e.g., logistical limitations such asno or limited access to a swimming pool, a car, or a particular textbook) associated with at least one of the one or more end users 4*.

In the same or different implementations, operation 542 may include anoperation 544 for developing the template by including into the templateat least one emulatable aspect that was derived based, at least in part,on the plurality of relevant reported aspects that are each associatedwith a different source user, the at least one emulatable aspect beingdetermined to be compliant with one or more personal limitationsassociated with at least one of the one or more end users as depicted inFIG. 5 b. For instance, the template developing module 104 of thecomputing device 10 developing the template 16 by having the emulatableaspect including module 216 include into the template 16 at least oneemulatable aspect that was derived by the emulatable aspect derivingmodule 218 based, at least in part, on the plurality of relevantreported aspects 14* that are each associated with a different sourceuser 2*, the at least one emulatable aspect being determined (e.g., asdetermined by the compliant determining module 228) to be compliant withone or more personal limitations (e.g., dietary or religiouslimitations) associated with at least one of the one or more end users4*.

In the same or different implementations, operation 542 may include anoperation 545 for developing the template by including into the templateat least one emulatable aspect that was derived based, at least in part,on the plurality of relevant reported aspects that are each associatedwith a different source user, the at least one emulatable aspect beingdetermined to be compliant with one or more physical limitationsassociated with at least one of the one or more end users as depicted inFIG. 5 c. For instance, the template developing module 104 of thecomputing device 10 developing the template 16 by having the emulatableaspect including module 216 include into the template 16 at least oneemulatable aspect that was derived by the emulatable aspect derivingmodule 218 based, at least in part, on the plurality of relevantreported aspects 14* that are each associated with a different sourceuser 2*, the at least one emulatable aspect being determined (e.g., asdetermined by the compliant determining module 228) to be compliant withone or more physical limitations (e.g., having severe arthritis)associated with at least one of the one or more end users 4*.

In the same or different implementations, operation 542 may include anoperation 546 for developing the template by including into the templateat least one emulatable aspect that was derived based, at least in part,on the plurality of relevant reported aspects that are each associatedwith a different source user, the at least one emulatable aspect beingdetermined to be compliant with one or more medical or healthlimitations associated with at least one of the one or more end users asdepicted in FIG. 5 c. For instance, the template developing module 104of the computing device 10 developing the template 16 by having theemulatable aspect including module 216 include into the template 16 atleast one emulatable aspect that was derived by the emulatable aspectderiving module 218 based, at least in part, on the plurality ofrelevant reported aspects 14* that are each associated with a differentsource user 2*, the at least one emulatable aspect being determined(e.g., as determined by the compliant determining module 228) to becompliant with one or more medical or health limitations (e.g., beinglactose intolerant, being diabetic, or being in poor physical shape)associated with at least one of the one or more end users 4*.

In the same or different implementations, operation 542 may include anoperation 547 for developing the template by including into the templateat least one emulatable aspect that was derived based, at least in part,on the plurality of relevant reported aspects that are each associatedwith a different source user, the at least one emulatable aspect beingdetermined to be compliant with one or more user state limitationsassociated with at least one of the one or more end users as depicted inFIG. 5 c. For instance, the template developing module 104 of thecomputing device 10 developing the template 16 by having the emulatableaspect including module 216 include into the template 16 at least oneemulatable aspect that was derived by the emulatable aspect derivingmodule 218 based, at least in part, on the plurality of relevantreported aspects 14* that are each associated with a different sourceuser 2*, the at least one emulatable aspect being determined (e.g., asdetermined by the compliant determining module 228) to be compliant withone or more user state limitations (e.g., being married, beingunemployed, or being mentally or physically fatigued) associated with atleast one of the one or more end users 4*.

In the same or different implementations, operation 542 may include anoperation 548 for developing the template by including into the templateat least one emulatable aspect that was derived based, at least in part,on the plurality of relevant reported aspects that are each associatedwith a different source user, the at least one emulatable aspect beingdetermined to be compliant with one or more legal or regulatorylimitations associated with at least one of the one or more end users asdepicted in FIG. 5 c. For instance, the template developing module 104of the computing device 10 developing the template 16 by having theemulatable aspect including module 216 include into the template 16 atleast one emulatable aspect that was derived by the emulatable aspectderiving module 218 based, at least in part, on the plurality ofrelevant reported aspects 14* that are each associated with a differentsource user 2*, the at least one emulatable aspect being determined(e.g., as determined by the compliant determining module 228) to becompliant with one or more legal or regulatory limitations (e.g., localdrug regulations) associated with at least one of the one or more endusers 4*.

In the same or different implementations, operation 542 may include anoperation 549 for developing the template by including into the templateat least one emulatable aspect that was derived based, at least in part,on the plurality of relevant reported aspects that are each associatedwith a different source user, the at least one emulatable aspect beingdetermined to be compliant with one or more academic or intellectuallimitations associated with at least one of the one or more end users asdepicted in FIG. 5 d. For instance, the template developing module 104of the computing device 10 developing the template 16 by having theemulatable aspect including module 216 include into the template 16 atleast one emulatable aspect that was derived by the emulatable aspectderiving module 218 based, at least in part, on the plurality ofrelevant reported aspects 14* that are each associated with a differentsource user 2*, the at least one emulatable aspect being determined(e.g., as determined by the compliant determining module 228) to becompliant with one or more academic or intellectual limitations (e.g.,lacks particular educational or training background) associated with atleast one of the one or more end users 4*.

In the same or different implementations, operation 533 may include anoperation 550 for developing the template by including into the templateat least one emulatable aspect that was derived based, at least in part,on the plurality of relevant reported aspects that are each associatedwith different source users, the at least one emulatable aspect beingdetermined to be at least one plausible emulatable aspect that has beensuccessfully emulated by one or more third parties who share at leastone common trait with the one or more end users as depicted in FIG. 5 d.For instance, the template developing module 104 of the computing device10 developing the template 16 by having the emulatable aspect includingmodule 216 include into the template 16 at least one emulatable aspectthat was derived by the emulatable aspect deriving module 218 based, atleast in part, on the plurality of relevant reported aspects 14* thatare each associated with different source users 2*, the at least oneemulatable aspect being determined (e.g., as determined by the plausibleemulatable aspect determining module 230) to be at least one plausibleemulatable aspect that has been successfully emulated by one or morethird parties 6 who share at least one common trait (e.g., ethnicity orillness) with the one or more end users 4*.

In the same or different implementations, operation 533 may include anoperation 551 for developing the template by including into the templateat least one emulatable aspect that was derived based, at least in part,on the plurality of relevant reported aspects that are each associatedwith different source users, the at least one emulatable aspect beingdetermined to be at least one plausible emulatable aspect that has beensuccessfully emulated by one or more third parties in order to achievethe one or more target outcomes as depicted in FIG. 5 d. For instance,the template developing module 104 of the computing device 10 developingthe template 16 by having the emulatable aspect including module 216include into the template 16 at least one emulatable aspect that wasderived by the emulatable aspect deriving module 218 based, at least inpart, on the plurality of relevant reported aspects 14* that are eachassociated with different source users 2*, the at least one emulatableaspect being determined (e.g., as determined by the plausible emulatableaspect determining module 230) to be at least one plausible emulatableaspect that has been successfully emulated by one or more third parties6 in order to achieve the one or more target outcomes.

In various implementations, the template 16 that is developed throughthe template developing operation 304 of FIG. 3 may be designed tofacilitate achievement of any one or more of a variety of targetoutcomes. For example, in some implementations, the template developingoperation 304 may include an operation 552 for developing the templatedesigned to facilitate the one or more end users to achieve the one ormore target outcomes including one or more health or medical outcomes asdepicted in FIG. 5 e. For instance, the template developing module 104of the computing device 10 developing the template 16 designed tofacilitate the one or more end users 4* to achieve the one or moretarget outcomes including one or more health or medical outcomes (e.g.,losing weight, improve results of a medical treatment, reduce pain,reduce stress, reduce blood pressure or blood glucose levels, and soforth).

In the same or different implementations, the template developingoperation 304 may include an operation 553 for developing the templatedesigned to facilitate the one or more end users to achieve the one ormore target outcomes including one or more athletic or gaming outcomesas depicted in FIG. 5 e. For instance, the template developing module104 of the computing device 10 developing the template 16 designed tofacilitate the one or more end users 4* to achieve the one or moretarget outcomes including one or more athletic or gaming outcomes (e.g.,win a tennis tournament, lower golf handicap, improve scores on anelectronic game, and so forth).

In the same or different implementations, the template developingoperation 304 may include an operation 554 for developing the templatedesigned to facilitate the one or more end users to achieve the one ormore target outcomes including one or more occupational outcomes asdepicted in FIG. 5 e. For instance, the template developing module 104of the computing device 10 developing the template 16 designed tofacilitate the one or more end users 4* to achieve the one or moretarget outcomes including one or more occupational outcomes (e.g.,complete a work project, getting a new client, obtaining a promotion,and so forth).

In the same or different implementations, the template developingoperation 304 may include an operation 555 for developing the templatedesigned to facilitate the one or more end users to achieve the one ormore target outcomes including one or more social or leisure outcomes asdepicted in FIG. 5 e. For instance, the template developing module 104of the computing device 10 developing the template 16 designed tofacilitate the one or more end users 4* to achieve the one or moretarget outcomes including one or more social or leisure outcomes (e.g.,invited to be a member of an elite social organization, acquiring newfriends, and so forth).

In the same or different implementations, the template developingoperation 304 may include an operation 556 for developing the templatedesigned to facilitate the one or more end users to achieve the one ormore target outcomes including one or more sexual intimacy outcomes asdepicted in FIG. 5 e. For instance, the template developing module 104of the computing device 10 developing the template 16 designed tofacilitate the one or more end users 4* to achieve the one or moretarget outcomes including one or more sexual intimacy outcomes (e.g.,increase the frequency of sexual encounters).

In the same or different implementations, the template developingoperation 304 may include an operation 557 for developing the templatedesigned to facilitate the one or more end users to achieve the one ormore target outcomes including one or more academic or intellectualoutcomes as depicted in FIG. 5 e. For instance, the template developingmodule 104 of the computing device 10 developing the template 16designed to facilitate the one or more end users 4* to achieve the oneor more target outcomes including one or more academic or intellectualoutcomes (e.g., understanding particular concepts introduced in a book,accepted for enrollment at a particular University, and so forth).

In the same or different implementations, the template developingoperation 304 may include an operation 558 for developing the templatedesigned to facilitate the one or more end users to achieve the one ormore target outcomes including one or more spiritual or religiousoutcomes as depicted in FIG. 5 e. For instance, the template developingmodule 104 of the computing device 10 developing the template 16designed to facilitate the one or more end users 4* to achieve the oneor more target outcomes including one or more spiritual or religiousoutcomes (e.g., achieve spiritual harmony, acceptance to a particularchurch or religion, and so forth).

In the same or different implementations, the template developingoperation 304 may include an operation 559 for developing the templatedesigned to facilitate the one or more end users to achieve the one ormore target outcomes including one or more user state outcomes asdepicted in FIG. 5 e. For instance, the template developing module 104of the computing device 10 developing the template 16 designed tofacilitate the one or more end users 4* to achieve the one or moretarget outcomes including one or more user state outcomes (e.g., achievecertain subjective user states such as being “happy” or “content,”achieve certain social states such as being married, and so forth).

Referring to FIG. 6 illustrating another operational flow 600 inaccordance with various embodiments. Operational flow 600 includescertain operations that mirror the operations included in theoperational flow 300 of FIG. 3. These operations include a relevantreported aspect providing operation 602 and a template developingoperation 604 that corresponds to and mirror the relevant reportedaspect providing operation 302 and the template developing operation304, respectively, of FIG. 3.

In addition, operational flow 600 includes a template presentingoperation 606 for presenting the template as depicted in FIG. 6. Forinstance, the template presenting module 106 of the computing device 10presenting the template 16 resulting from the template developingoperation 604.

In some implementations, the template presenting operation 606 of FIG. 6may include an operation 761 for transmitting the template via one ormore communication networks as depicted in FIG. 7. For instance, thetemplate transmitting module 150 (see FIG. 1 b) of the computing device10 transmitting the template 16 via one or more communication networks50.

In the same or different implementations, the template presentingoperation 606 may include an operation 762 for indicating the templatevia a user interface as depicted in FIG. 7. For instance, the templateindicating module 152 of the computing device 10 indicating the template16 via a user interface 120 (e.g., a display monitor, a touch screen,one or more speakers, and so forth).

In the same or different implementations, the template presentingoperation 606 may include an operation 763 for presenting the templateto the one or more end users as depicted in FIG. 7. For instance, thetemplate presenting module 106 of the computing device 10 presenting thetemplate 16 to the one or more end users 4*.

In the same or different implementations, the template presentingoperation 606 may include an operation 764 for presenting the templateto one or more third parties as depicted in FIG. 7. For instance, thetemplate presenting module 106 of the computing device 10 presenting thetemplate 16 to one or more third parties 6 (e.g., health or medicalentities such as a doctor's office, a future end user 4*, and so forth).

Turning now to FIG. 8, which is a high-level block diagram illustratinga particular implementation of the computing device 10 of FIG. 1 b. Asillustrated, the computing device 10 may include a processor 802 (e.g.,microprocessor, controller, and so forth) coupled to a storage medium806 (e.g., volatile or non-volatile memory). The storage medium 806 maystore computer readable instructions 804 (e.g., computer programproduct). The processor 802, in various implementations, may execute thecomputer readable instructions 804 in order to execute one or moreoperations described above and as illustrated in FIGS. 3, 4 a, 4 b, 4 c,4 d, 4 e, 5 a, 5 b, 5 c, 5 d, 5 e, 6, and 7.

For example, the processor 802 may execute the computer readableinstructions 804 in order to provide a plurality of relevant reportedaspects 14 associated with a plurality of source users 2* that arerelevant to achieving one or more target outcomes, the providing of theplurality of relevant reported aspects 14 being based, at least in part,on relevancy of the plurality of relevant reported aspects 14 withrespect to the one or more target outcomes; and/or to develop a template16 designed to facilitate one or more end users 4* to achieve the one ormore target outcomes when one or more emulatable aspects included in thetemplate 16 are emulated, the development of the template 16 beingbased, at least in part, on the providing of the plurality of relevantreported aspects 14 associated with the plurality of source users 2* asillustrated by the operational flow 300 of FIG. 3.

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware and software implementations of aspects of systems; theuse of hardware or software is generally (but not always, in that incertain contexts the choice between hardware and software can becomesignificant) a design choice representing cost vs. efficiency tradeoffs.Those having skill in the art will appreciate that there are variousvehicles by which processes and/or systems and/or other technologiesdescribed herein can be effected (e.g., hardware, software, and/orfirmware), and that the preferred vehicle will vary with the context inwhich the processes and/or systems and/or other technologies aredeployed. For example, if an implementer determines that speed andaccuracy are paramount, the implementer may opt for a mainly hardwareand/or firmware vehicle; alternatively, if flexibility is paramount, theimplementer may opt for a mainly software implementation; or, yet againalternatively, the implementer may opt for some combination of hardware,software, and/or firmware. Hence, there are several possible vehicles bywhich the processes and/or devices and/or other technologies describedherein may be effected, none of which is inherently superior to theother in that any vehicle to be utilized is a choice dependent upon thecontext in which the vehicle will be deployed and the specific concerns(e.g., speed, flexibility, or predictability) of the implementer, any ofwhich may vary. Those skilled in the art will recognize that opticalaspects of implementations will typically employ optically-orientedhardware, software, and or firmware.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof. In one embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuitry (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuitry, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, and that designingthe circuitry and/or writing the code for the software and or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies regardless of the particular type of signal bearing medium usedto actually carry out the distribution. Examples of a signal bearingmedium include, but are not limited to, the following: a recordable typemedium such as a floppy disk, a hard disk drive, a Compact Disc (CD), aDigital Video Disk (DVD), a digital tape, a computer memory, etc.; and atransmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link, etc.).

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware, orany combination thereof can be viewed as being composed of various typesof “electrical circuitry.” Consequently, as used herein “electricalcircuitry” includes, but is not limited to, electrical circuitry havingat least one discrete electrical circuit, electrical circuitry having atleast one integrated circuit, electrical circuitry having at least oneapplication specific integrated circuit, electrical circuitry forming ageneral purpose computing device configured by a computer program (e.g.,a general purpose computer configured by a computer program which atleast partially carries out processes and/or devices described herein,or a microprocessor configured by a computer program which at leastpartially carries out processes and/or devices described herein),electrical circuitry forming a memory device (e.g., forms of randomaccess memory), and/or electrical circuitry forming a communicationsdevice (e.g., a modem, communications switch, or optical-electricalequipment). Those having skill in the art will recognize that thesubject matter described herein may be implemented in an analog ordigital fashion or some combination thereof.

Those having skill in the art will recognize that it is common withinthe art to describe devices and/or processes in the fashion set forthherein, and thereafter use engineering practices to integrate suchdescribed devices and/or processes into data processing systems. Thatis, at least a portion of the devices and/or processes described hereincan be integrated into a data processing system via a reasonable amountof experimentation. Those having skill in the art will recognize that atypical data processing system generally includes one or more of asystem unit housing, a video display device, a memory such as volatileand non-volatile memory, processors such as microprocessors and digitalsignal processors, computational entities such as operating systems,drivers, graphical user interfaces, and applications programs, one ormore interaction devices, such as a touch pad or screen, and/or controlsystems including feedback loops and control motors (e.g., feedback forsensing position and/or velocity; control motors for moving and/oradjusting components and/or quantities). A typical data processingsystem may be implemented utilizing any suitable commercially availablecomponents, such as those typically found in datacomputing/communication and/or network computing/communication systems.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled”, to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable”, to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents.

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of the subject matter described herein.Furthermore, it is to be understood that the invention is defined by theappended claims.

It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to inventions containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations.

In addition, even if a specific number of an introduced claim recitationis explicitly recited, those skilled in the art will recognize that suchrecitation should typically be interpreted to mean at least the recitednumber (e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations). Furthermore, in those instances where a conventionanalogous to “at least one of A, B, and C, etc.” is used, in generalsuch a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, and C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.).

In those instances where a convention analogous to “at least one of A,B, or C, etc.” is used, in general such a construction is intended inthe sense one having skill in the art would understand the convention(e.g., “a system having at least one of A, B, or C” would include butnot be limited to systems that have A alone, B alone, C alone, A and Btogether, A and C together, B and C together, and/or A, B, and Ctogether, etc.). It will be further understood by those within the artthat virtually any disjunctive word and/or phrase presenting two or morealternative terms, whether in the description, claims, or drawings,should be understood to contemplate the possibilities of including oneof the terms, either of the terms, or both terms. For example, thephrase “A or B” will be understood to include the possibilities of “A”or “B” or “A and B.”

1. A computationally-implemented system, comprising: means for providinga plurality of relevant reported aspects associated with a plurality ofsource users that are relevant to achieving one or more target outcomes,the providing of the plurality of relevant reported aspects being based,at least in part, on relevancy of the plurality of relevant reportedaspects with respect to the one or more target outcomes; and means fordeveloping a template designed to facilitate one or more end users toachieve the one or more target outcomes when one or more emulatableaspects included in the template are emulated, the development of thetemplate being based, at least in part, on the providing of theplurality of relevant reported aspects associated with the plurality ofsource users, wherein said means for developing a template designed tofacilitate one or more end users to achieve the one or more targetoutcomes when one or more emulatable aspects included in the templateare emulated, the development of the template being based, at least inpart, on the providing of the plurality of relevant reported aspectsassociated with the plurality of source users, comprises: means fordeveloping the template by including into the template one or moreemulatable aspects that were derived based, at least in part, on theplurality of relevant reported aspects that are associated with theplurality of source users and that are relevant to achieving the one ormore target outcomes, wherein said means for developing the template byincluding into the template one or more emulatable aspects that werederived based, at least in part, on the plurality of relevant reportedaspects that are associated with the plurality of source users and thatare relevant to achieving the one or more target outcomes, comprises:means for developing the template by including into the template atleast one emulatable aspect that was derived based, at least in part, ona plurality of relevant reported aspects that are each associated withdifferent source users, wherein said means for developing the templateby including into the template at least one emulatable aspect that wasderived based, at least in part, on a plurality of relevant reportedaspects that are each associated with different source users, comprises:means for developing the template by including into the template atleast one emulatable aspect that was derived based, at least in part, onthe plurality of relevant reported aspects that are each associated withdifferent source users, the at least one emulatable aspect beingdetermined to be at least one plausible emulatable aspect that has beensuccessfully emulated by one or more third parties who share at leastone common trait with the one or more end users.
 2. Thecomputationally-implemented system of claim 1, wherein said means forproviding a plurality of relevant reported aspects associated with aplurality of source users that are relevant to achieving one or moretarget outcomes, the providing of the plurality of relevant reportedaspects being based, at least in part, on relevancy of the plurality ofrelevant reported aspects with respect to the one or more targetoutcomes, comprises: means for providing the plurality of relevantreported aspects by at least identifying reported aspects thatcorrespond to the one or more target outcomes.
 3. Thecomputationally-implemented system of claim 2, wherein said means forproviding the plurality of relevant reported aspects by at leastidentifying reported aspects that correspond to the one or more targetoutcomes, comprises: means for identifying the source users based on thesource users association with the reported aspects that corresponds tothe one or more target outcomes.
 4. The computationally-implementedsystem of claim 3, wherein said means for identifying the source usersbased on the source users association with the reported aspects thatcorresponds to the one or more target outcomes, comprises: means forproviding reported aspects that are at least associated with theidentified source users.
 5. The computationally-implemented system ofclaim 4, wherein said means for providing reported aspects that are atleast associated with the identified source users, comprises: means forproviding, from the reported aspects that are at least associated withthe identified source users, reported aspects that are relevant withrespect to one or more relevancy factors.
 6. Thecomputationally-implemented system of claim 5, wherein said means forproviding, from the reported aspects that are at least associated withthe identified source users, reported aspects that are relevant withrespect to one or more relevancy factors, comprises: means for providingthe reported aspects that are relevant with respect to the one or morerelevancy factors by providing reported aspects that are at leastassociated with the identified source users and that belong to one ormore aspect types that are of interest to one or more end users.
 7. Thecomputationally-implemented system of claim 5, wherein said means forproviding, from the reported aspects that are at least associated withthe identified source users, reported aspects that are relevant withrespect to one or more relevancy factors, comprises: means for providingthe reported aspects that are relevant with respect to the one or morerelevancy factors by providing reported aspects that are at leastassociated with the identified source users and that belong to one ormore aspect types that have been indicated by at least one source useras being relevant to the achievement of the one or more target outcomes.8. The computationally-implemented system of claim 5, wherein said meansfor providing, from the reported aspects that are at least associatedwith the identified source users, reported aspects that are relevantwith respect to one or more relevancy factors, comprises: means forproviding the reported aspects that are relevant with respect to the oneor more relevancy factors by providing reported aspects that are atleast associated with the identified source users and that belong to oneor more aspect types that have been indicated by at least one thirdparty source as being relevant to the achievement of the one or moretarget outcomes.
 9. The computationally-implemented system of claim 5,wherein said means for providing, from the reported aspects that are atleast associated with the identified source users, reported aspects thatare relevant with respect to one or more relevancy factors, comprises:means for providing the reported aspects that are relevant with respectto the one or more relevancy factors by providing reported aspects thatare at least associated with the identified source users and thatindicate aspects of the identified source users that occurred within oneor more predefined time periods, respectively, from occurrences of thereported aspects that were identified as corresponding to the one ormore target outcomes.
 10. The computationally-implemented system ofclaim 9, wherein said means for providing the reported aspects that arerelevant with respect to the one or more relevancy factors by providingreported aspects that are at least associated with the identified sourceusers and that indicate aspects of the identified source users thatoccurred within one or more predefined time periods, respectively, fromoccurrences of the reported aspects that were identified ascorresponding to the one or more target outcomes, comprises: means forproviding the reported aspects that are relevant with respect to the oneor more relevancy factors by providing reported aspects that are atleast associated with the identified source users and that indicateaspects of the identified source users that occurred prior to and withinone or more predefined time periods, respectively, from occurrences ofthe reported aspects that were identified as corresponding to the one ormore target outcomes.
 11. The computationally-implemented system ofclaim 1, wherein said means for providing a plurality of relevantreported aspects associated with a plurality of source users that arerelevant to achieving one or more target outcomes, the providing of theplurality of relevant reported aspects being based, at least in part, onrelevancy of the plurality of relevant reported aspects with respect tothe one or more target outcomes, comprises: means for providing theplurality of relevant reported aspects associated with the plurality ofsource users that are relevant to achieving one or more target outcomesincluding one or more relevant reported aspects that were at leastoriginally reported via one or more log entries.
 12. Thecomputationally-implemented system of claim 11, wherein said means forproviding the plurality of relevant reported aspects associated with theplurality of source users that are relevant to achieving one or moretarget outcomes including one or more relevant reported aspects thatwere at least originally reported via one or more log entries,comprises: means for providing the plurality of relevant reportedaspects associated with the plurality of source users that are relevantto achieving one or more target outcomes including one or more relevantreported aspects that were at least originally reported via one or moresocial networking entries.
 13. The computationally-implemented system ofclaim 12, wherein said means for providing the plurality of relevantreported aspects associated with the plurality of source users that arerelevant to achieving one or more target outcomes including one or morerelevant reported aspects that were at least originally reported via oneor more social networking entries, comprises: means for providing theplurality of relevant reported aspects associated with the plurality ofsource users that are relevant to achieving one or more target outcomesincluding one or more relevant reported aspects that were at leastoriginally reported via one or more blog entries.
 14. Thecomputationally-implemented system of claim 12, wherein said means forproviding the plurality of relevant reported aspects associated with theplurality of source users that are relevant to achieving one or moretarget outcomes including one or more relevant reported aspects thatwere at least originally reported via one or more social networkingentries, comprises: means for providing the plurality of relevantreported aspects associated with the plurality of source users that arerelevant to achieving one or more target outcomes including one or morerelevant reported aspects that were at least originally reported via oneor more status reports.
 15. The computationally-implemented system ofclaim 11, wherein said means for providing the plurality of relevantreported aspects associated with the plurality of source users that arerelevant to achieving one or more target outcomes including one or morerelevant reported aspects that were at least originally reported via oneor more log entries, comprises: means for providing the plurality ofrelevant reported aspects associated with the plurality of source usersthat are relevant to achieving one or more target outcomes including oneor more relevant reported aspects that were at least originally reportedvia one or more journal entries.
 16. The computationally-implementedsystem of claim 11, wherein said means for providing the plurality ofrelevant reported aspects associated with the plurality of source usersthat are relevant to achieving one or more target outcomes including oneor more relevant reported aspects that were at least originally reportedvia one or more log entries, comprises: means for providing theplurality of relevant reported aspects associated with the plurality ofsource users that are relevant to achieving one or more target outcomesincluding one or more relevant reported aspects that were at leastoriginally reported by one or more of the source users.
 17. Thecomputationally-implemented system of claim 11, wherein said means forproviding the plurality of relevant reported aspects associated with theplurality of source users that are relevant to achieving one or moretarget outcomes including one or more relevant reported aspects thatwere at least originally reported via one or more log entries,comprises: means for providing the plurality of relevant reportedaspects associated with the plurality of source users that are relevantto achieving one or more target outcomes including one or more relevantreported aspects that were at least originally reported by one or morethird parties.
 18. The computationally-implemented system of claim 11,wherein said means for providing the plurality of relevant reportedaspects associated with the plurality of source users that are relevantto achieving one or more target outcomes including one or more relevantreported aspects that were at least originally reported via one or morelog entries, comprises: means for providing the plurality of relevantreported aspects associated with the plurality of source users that arerelevant to achieving one or more target outcomes including one or morerelevant reported aspects that were at least originally reported by oneor more sensors.
 19. The computationally-implemented system of claim 1,wherein said means for providing a plurality of relevant reportedaspects associated with a plurality of source users that are relevant toachieving one or more target outcomes, the providing of the plurality ofrelevant reported aspects being based, at least in part, on relevancy ofthe plurality of relevant reported aspects with respect to the one ormore target outcomes, comprises: means for providing the plurality ofrelevant reported aspects including providing a first one or morereported aspects that are associated with a first source user and thatare relevant to achieving at least one of the one or more targetoutcomes and providing a second one or more reported aspects that areassociated with a second source user and that are relevant to achievingthe at least one of the one or more target outcomes, the providing ofthe first one or more reported aspects and the second one or morereported aspects being based on the first one or more reported aspects'and the second one or more reported aspects' relevancy with respect tothe at least one of the one or more target outcomes.
 20. Thecomputationally-implemented system of claim 1, wherein said means forproviding a plurality of relevant reported aspects associated with aplurality of source users that are relevant to achieving one or moretarget outcomes, the providing of the plurality of relevant reportedaspects being based, at least in part, on relevancy of the plurality ofrelevant reported aspects with respect to the one or more targetoutcomes, comprises: means for providing the plurality of relevantreported aspects including providing a plurality of relevant reportedaspects related to a plurality of behavior incidences associated withthe plurality of source users.
 21. The computationally-implementedsystem of claim 1, wherein said means for providing a plurality ofrelevant reported aspects associated with a plurality of source usersthat are relevant to achieving one or more target outcomes, theproviding of the plurality of relevant reported aspects being based, atleast in part, on relevancy of the plurality of relevant reportedaspects with respect to the one or more target outcomes, comprises:means for providing the plurality of relevant reported aspects includingproviding a plurality of relevant reported aspects related to aplurality of incidences of user beliefs associated with the plurality ofsource users.
 22. The computationally-implemented system of claim 1,wherein said means for providing a plurality of relevant reportedaspects associated with a plurality of source users that are relevant toachieving one or more target outcomes, the providing of the plurality ofrelevant reported aspects being based, at least in part, on relevancy ofthe plurality of relevant reported aspects with respect to the one ormore target outcomes, comprises: means for providing the plurality ofrelevant reported aspects including providing a plurality of relevantreported aspects related to a plurality of incidences of user statesassociated with the plurality of source users.
 23. Thecomputationally-implemented system of claim 1, wherein said means forproviding a plurality of relevant reported aspects associated with aplurality of source users that are relevant to achieving one or moretarget outcomes, the providing of the plurality of relevant reportedaspects being based, at least in part, on relevancy of the plurality ofrelevant reported aspects with respect to the one or more targetoutcomes, comprises: means for providing the plurality of relevantreported aspects including providing a plurality of relevant reportedaspects related to a plurality of incidences of user physicalcharacteristics associated with the plurality of source users.
 24. Thecomputationally-implemented system of claim 1, wherein said means forproviding a plurality of relevant reported aspects associated with aplurality of source users that are relevant to achieving one or moretarget outcomes, the providing of the plurality of relevant reportedaspects being based, at least in part, on relevancy of the plurality ofrelevant reported aspects with respect to the one or more targetoutcomes, comprises: means for providing the plurality of relevantreported aspects including providing a plurality of relevant reportedaspects related to a plurality of incidences of user locationsassociated with the plurality of source users.
 25. Thecomputationally-implemented system of claim 1, wherein said means forproviding a plurality of relevant reported aspects associated with aplurality of source users that are relevant to achieving one or moretarget outcomes, the providing of the plurality of relevant reportedaspects being based, at least in part, on relevancy of the plurality ofrelevant reported aspects with respect to the one or more targetoutcomes, comprises: means for providing the plurality of relevantreported aspects including providing a plurality of relevant reportedaspects related to a plurality of incidences of external eventsassociated with the plurality of source users.
 26. Thecomputationally-implemented system of claim 1, wherein said means fordeveloping the template by including into the template at least oneemulatable aspect that was derived based, at least in part, on aplurality of relevant reported aspects that are each associated withdifferent source users, comprises: means for developing the template byincluding into the template at least one emulatable aspect that wasderived based, at least in part, on a first relevant reported aspectthat is associated with a first source user and a second relevantreported aspect that is associated with a second source user.
 27. Thecomputationally-implemented system of claim 26, wherein said means fordeveloping the template by including into the template at least oneemulatable aspect that was derived based, at least in part, on a firstrelevant reported aspect that is associated with a first source user anda second relevant reported aspect that is associated with a secondsource user, comprises: means for developing the template by includinginto the template a second emulatable aspect that was derived based, atleast in part, on a third relevant reported aspect that is associatedwith the first source user and a fourth relevant reported aspect that isassociated with the second source user.
 28. Thecomputationally-implemented system of claim 26, wherein said means fordeveloping the template by including into the template at least oneemulatable aspect that was derived based, at least in part, on a firstrelevant reported aspect that is associated with a first source user anda second relevant reported aspect that is associated with a secondsource user, comprises: means for developing the template by includinginto the template a second emulatable aspect that was derived based, atleast in part, on a third relevant reported aspect that is associatedwith a third source user and a fourth relevant reported aspect that isassociated with a fourth source user.
 29. Thecomputationally-implemented system of claim 1, wherein said means fordeveloping the template by including into the template at least oneemulatable aspect that was derived based, at least in part, on aplurality of relevant reported aspects that are each associated withdifferent source users, comprises: means for developing the template byincluding into the template at least one emulatable aspect thatcorresponds to a commonly reported aspect that is determined to beassociated with two or more of the plurality of source users.
 30. Thecomputationally-implemented system of claim 29, wherein said means fordeveloping the template by including into the template at least oneemulatable aspect that corresponds to a commonly reported aspect that isdetermined to be associated with two or more of the plurality of sourceusers, comprises: means for developing the template by including intothe template at least one emulatable aspect that corresponds to acommonly reported aspect that is determined to be associated with amajority of the plurality of source users.
 31. Thecomputationally-implemented system of claim 1, wherein said means fordeveloping the template by including into the template at least oneemulatable aspect that was derived based, at least in part, on aplurality of relevant reported aspects that are each associated withdifferent source users, comprises: means for developing the template byincluding into the template at least one emulatable aspect that includesat least a portion that was derived based, at least in part, ondeviations of the plurality of relevant reported aspects with respect toeach other.
 32. The computationally-implemented system of claim 31,wherein said means for developing the template by including into thetemplate at least one emulatable aspect that includes at least a portionthat was derived based, at least in part, on deviations of the pluralityof relevant reported aspects with respect to each other, comprises:means for developing the template by including into the template atleast one mean value emulatable aspect that was at least partiallydeveloped by determining a mean value for the plurality of relevantreported aspects.
 33. The computationally-implemented system of claim31, wherein said means for developing the template by including into thetemplate at least one emulatable aspect that includes at least a portionthat was derived based, at least in part, on deviations of the pluralityof relevant reported aspects with respect to each other, comprises:means for developing the template by including into the template atleast one average value emulatable aspect that was at least partiallydeveloped by determining an average value for the plurality of relevantreported aspects.
 34. The computationally-implemented system of claim 1,wherein said means for developing the template by including into thetemplate at least one emulatable aspect that was derived based, at leastin part, on a plurality of relevant reported aspects that are eachassociated with different source users, comprises: means for developingthe template by including into the template at least one emulatableaspect that was derived based, at least in part, on the plurality ofrelevant reported aspects that are each associated with a differentsource user, the at least one emulatable aspect being determined to becompliant with one or more limitations associated with at least one ofthe one or more end users.
 35. The computationally-implemented system ofclaim 1, wherein said means for developing the template by includinginto the template at least one emulatable aspect that was derived based,at least in part, on a plurality of relevant reported aspects that areeach associated with different source users, comprises: means fordeveloping the template by including into the template at least oneemulatable aspect that was derived based, at least in part, on theplurality of relevant reported aspects that are each associated withdifferent source users, the at least one emulatable aspect beingdetermined to be at least one plausible emulatable aspect that has beensuccessfully emulated by one or more third parties in order to achievethe one or more target outcomes.
 36. The computationally-implementedsystem of claim 1, wherein said means for developing a template designedto facilitate one or more end users to achieve the one or more targetoutcomes when one or more emulatable aspects included in the templateare emulated, the development of the template being based, at least inpart, on the providing of the plurality of relevant reported aspectsassociated with the plurality of source users, comprises: means fordeveloping the template designed to facilitate the one or more end usersto achieve the one or more target outcomes including one or more healthor medical outcomes.
 37. The computationally-implemented system of claim1, wherein said means for developing a template designed to facilitateone or more end users to achieve the one or more target outcomes whenone or more emulatable aspects included in the template are emulated,the development of the template being based, at least in part, on theproviding of the plurality of relevant reported aspects associated withthe plurality of source users, comprises: means for developing thetemplate designed to facilitate the one or more end users to achieve theone or more target outcomes including one or more athletic or gamingoutcomes.
 38. The computationally-implemented system of claim 1, whereinsaid means for developing a template designed to facilitate one or moreend users to achieve the one or more target outcomes when one or moreemulatable aspects included in the template are emulated, thedevelopment of the template being based, at least in part, on theproviding of the plurality of relevant reported aspects associated withthe plurality of source users, comprises: means for developing thetemplate designed to facilitate the one or more end users to achieve theone or more target outcomes including one or more occupational outcomes.39. The computationally-implemented system of claim 1, wherein saidmeans for developing a template designed to facilitate one or more endusers to achieve the one or more target outcomes when one or moreemulatable aspects included in the template are emulated, thedevelopment of the template being based, at least in part, on theproviding of the plurality of relevant reported aspects associated withthe plurality of source users, comprises: means for developing thetemplate designed to facilitate the one or more end users to achieve theone or more target outcomes including one or more social or leisureoutcomes.
 40. The computationally-implemented system of claim 1, whereinsaid means for developing a template designed to facilitate one or moreend users to achieve the one or more target outcomes when one or moreemulatable aspects included in the template are emulated, thedevelopment of the template being based, at least in part, on theproviding of the plurality of relevant reported aspects associated withthe plurality of source users, comprises: means for developing thetemplate designed to facilitate the one or more end users to achieve theone or more target outcomes including one or more academic orintellectual outcomes.
 41. The computationally-implemented system ofclaim 1, wherein said means for developing a template designed tofacilitate one or more end users to achieve the one or more targetoutcomes when one or more emulatable aspects included in the templateare emulated, the development of the template being based, at least inpart, on the providing of the plurality of relevant reported aspectsassociated with the plurality of source users, comprises: means fordeveloping the template designed to facilitate the one or more end usersto achieve the one or more target outcomes including one or more userstate outcomes.
 42. The computationally-implemented system of claim 1,further comprising: means for presenting the template.
 43. A method fordeveloping a template, comprising: providing a plurality of relevantreported aspects associated with a plurality of source users that arerelevant to achieving one or more target outcomes, the providing of theplurality of relevant reported aspects being based, at least in part, onrelevancy of the plurality of relevant reported aspects with respect tothe one or more target outcomes; and developing, by electricalcircuitry, a template designed to facilitate one or more end users toachieve the one or more target outcomes when one or more emulatableaspects included in the template are emulated, the development of thetemplate being based, at least in part, on the providing of theplurality of relevant reported aspects associated with the plurality ofsource users, wherein said developing, by electrical circuitry, atemplate designed to facilitate one or more end users to achieve the oneor more target outcomes when one or more emulatable aspects included inthe template are emulated, the development of the template being based,at least in part, on the providing of the plurality of relevant reportedaspects associated with the plurality of source users comprises:developing the template by including into the template one or moreemulatable aspects that were derived based, at least in part, on theplurality of relevant reported aspects that are associated with theplurality of source users and that are relevant to achieving the one ormore target outcomes, wherein said developing the template by includinginto the template one or more emulatable aspects that were derivedbased, at least in part, on the plurality of relevant reported aspectsthat are associated with the plurality of source users and that arerelevant to achieving the one or more target outcomes, comprises:developing the template by including into the template at least oneemulatable aspect that was derived based, at least in part, on aplurality of relevant reported aspects that are each associated withdifferent source users, wherein said developing the template byincluding into the template at least one emulatable aspect that wasderived based, at least in part, on a plurality of relevant reportedaspects that are each associated with different source users, comprises:developing the template by including into the template at least oneemulatable aspect that was derived based, at least in part, on theplurality of relevant reported aspects that are each associated withdifferent source users, the at least one emulatable aspect beingdetermined to be at least one plausible emulatable aspect that has beensuccessfully emulated by one or more third parties who share at leastone common trait with the one or more end users.
 44. A server,comprising: a relevant reported aspect providing module configured toprovide a plurality of relevant reported aspects associated with aplurality of source users that are relevant to achieving one or moretarget outcomes, the providing of the plurality of relevant reportedaspects being based, at least in part, on relevancy of the plurality ofrelevant reported aspects with respect to the one or more targetoutcomes; a template developing module configured to develop a templatedesigned to facilitate one or more end users to achieve the one or moretarget outcomes when one or more emulatable aspects included in thetemplate are emulated, the development of the template being based, atleast in part, on the providing of the plurality of relevant reportedaspects associated with the plurality of source users, wherein saidtemplate developing module comprises: an emulatable aspect includingmodule configured to include into the template one or more emulatableaspects that were derived by an emulatable aspect deriving module based,at least in part, on the plurality of relevant reported aspects that areassociated with the plurality of source users and that are relevant toachieving the one or more target outcomes, wherein said emulatableaspect including module comprises: an emulatable aspect deriving moduleconfigured to derive at least one emulatable aspect based, at least inpart, on a plurality of relevant reported aspects that are eachassociated with different source users, the at least one emulatableaspect to be included into the template, wherein said emulatable aspectderiving module comprises: a plausible emulatable aspect determiningmodule configured to determine whether at least one emulatable aspect tobe included in the template is at least one plausible emulatable aspectthat has been successfully emulated by one or more third parties whoshare at least one common trait with the one or more end users; and amemory.